narrowizard Github contribution chart
narrowizard Github Stats
narrowizard Most Used Languages

Activity

02 Oct 2022

Issue Comment

Narrowizard

[Bug][Jira] test connection api return success with a pair of any username and a valid token

Search before asking

  • [X] I had searched in the issues and found no similar issues.

What happened

I am using test connection api to check jira integration info before synchronizing.It always return success if the token is valid, even if the username is not exists.
But the jira tasks will fail with the wrong username.

What you expected to happen

Test connection api should keep consistent behaviour with sync tasks.
I mean, if test connection api is passed, sync tasks should not failed for authentication reason.

How to reproduce

Call test connection api with right endpoint, password but wrong username.

Anything else

This issue occurs both in jira server and jira cloud version.

Version

v0.12.0

Are you willing to submit PR?

  • [ ] Yes I am willing to submit a PR!

Code of Conduct

Forked On 02 Oct 2022 at 03:37:19

Narrowizard

please cherry-pick the fix to v0.12, thanks @mindlesscloud

Commented On 02 Oct 2022 at 03:37:19

Narrowizard

fix: overwrite startDate with the value of activatedDate

Summary

fix #3250 [Bug][Jira] sprint start date is wrong when using jira server Overwrite startDate with the value of activatedDate if it is available

Does this close any open issues?

Closes #3250

Screenshots

Include any relevant screenshots here.

Other Information

Any other information that is important to this PR.

Merged On 29 Sep 2022 at 03:26:13

Narrowizard

LGTM

Commented On 29 Sep 2022 at 03:26:13
Issue Comment

Narrowizard

[Bug][Jira] sprint start date is wrong when using jira server

Search before asking

  • [X] I had searched in the issues and found no similar issues.

What happened

I have synchronized jira data from my jira server (8.x), I find lake using sprints' planned start_date as sprints.start_date.

What you expected to happen

Expected to use sprints' activated date as sprints.start_date if sprints' activated date exist, otherwise sprints' planned start_date.

How to reproduce

Using devlake to sync jira data from a jira server.

Anything else

api response from jira server image

Version

v0.12.0

Are you willing to submit PR?

  • [ ] Yes I am willing to submit a PR!

Code of Conduct

Forked On 29 Sep 2022 at 02:56:20

Narrowizard

Further info: jira cloud has no activated date field in sprint api.

Commented On 29 Sep 2022 at 02:56:20
Issue Comment

Narrowizard

fix: use key as accountId

Summary

fix #3184 use key instead of email as the account ID

Does this close any open issues?

Closes #3184

Screenshots

Include any relevant screenshots here.

Other Information

Any other information that is important to this PR.

Forked On 27 Sep 2022 at 07:16:17

Narrowizard

LGTM

Commented On 27 Sep 2022 at 07:16:17

Narrowizard

started

Started On 21 Sep 2022 at 08:34:42
Create Branch

Narrowizard

Description not entered by the user.

On 11 Sep 2022 at 01:47:44

Narrowizard

Create docker-image.yml

Pushed On 11 Sep 2022 at 03:46:30

Narrowizard

chore: enhence dockerfile

Pushed On 09 Sep 2022 at 10:42:49

Narrowizard

chore: add docker file

Pushed On 09 Sep 2022 at 08:45:54

Narrowizard

started

Started On 06 Sep 2022 at 01:30:38

Narrowizard

started

Started On 30 Aug 2022 at 01:23:49
Issue Comment

Narrowizard

[Feature][Issue Tracking] Allow users to add their customized issue fields into domain schema

Search before asking

  • [X] I had searched in the issues and found no similar feature requirement.

Description

Comprehensive issue tracking tools, like Jira and TAPD, have a great ability to extend issue fields for users. Therefore, we should allow users to add these customized fields into domain schema, so that they can easily aggregate and analyze data by these fields without hassle.

Use case

In my Jira practice, I create many customized fields to manage and categorize issues. For example, our development team have several sub-team to take responsibility for different sub-system or components in our product. I create a field called "team" to help me allocate issues to each sub-team. And each sub-team only need to focus on their sub-backlog.

Obviously, the "team" field is not covered by domain layer and won't considered as a universal practice. But, when I dig in my issue data, "team" is an important dimensions to aggregate data and find the problem.

"team" is just an example. It could be "group", "issue reason", "importance", etc.

Related issues

No response

Are you willing to submit a PR?

  • [ ] Yes I am willing to submit a PR!

Code of Conduct

Forked On 29 Aug 2022 at 04:26:40

Narrowizard

Sounds it will update domain layer's table (like issues) schema, then how can we handle the db migration stuffs? eg:

  • conflicted custom fields
  • schema update in customize tasks

Commented On 29 Aug 2022 at 04:26:40

Narrowizard

started

Started On 20 Aug 2022 at 01:51:54

Narrowizard

started

Started On 20 Aug 2022 at 11:24:58

Narrowizard

started

Started On 20 Aug 2022 at 02:05:38

Narrowizard

started

Started On 20 Aug 2022 at 01:53:31

Narrowizard

started

Started On 20 Aug 2022 at 01:53:10

Narrowizard

fix: support multi type of story point field

Created On 17 Aug 2022 at 11:59:49
Create Branch
Narrowizard In narrowizard/incubator-devlake Create Branchfix/story_point

Narrowizard

Apache DevLake is an open-source dev data platform that ingests, analyzes, and visualizes the fragmented data from DevOps tools to distill insights for engineering productivity.

On 17 Aug 2022 at 11:59:21

Narrowizard

fix: support multi type of story point field (#2754)

Pushed On 17 Aug 2022 at 11:43:06

Narrowizard

fix: add getAfterResponse to overwrite by helper (#2755)

  • fix: fix afterResponse callback will overwrite by helper

  • fix: fix for ci

Co-authored-by: linyh yanghui@meri.co

Pushed On 17 Aug 2022 at 11:43:06

Narrowizard

fix: support multi type of story point field

Pushed On 17 Aug 2022 at 09:57:17
Issue Comment

Narrowizard

fix: support multi type of story point field

Summary

fix story point convert error

Does this close any open issues?

close #2753

Screenshots

Include any relevant screenshots here.

Other Information

A readable raw data diff:
image

Forked On 17 Aug 2022 at 09:35:20

Narrowizard

Pls take a look at this fix, and cherry-pick it to release-v0.12 branch after review and merge. @mindlesscloud @klesh

Commented On 17 Aug 2022 at 09:35:20

Narrowizard

fix: support multi type of story point field

Created On 17 Aug 2022 at 09:27:45
Create Branch
Narrowizard In narrowizard/incubator-devlake Create Branchfix/story_point

Narrowizard

Apache DevLake is an open-source dev data platform that ingests, analyzes, and visualizes the fragmented data from DevOps tools to distill insights for engineering productivity.

On 17 Aug 2022 at 09:26:47