incubator-devlake icon indicating copy to clipboard operation
incubator-devlake copied to clipboard

[Bug][Jira] When configuring the scope config in Jira Cloud, it is not possible to select the original types of issues.

Open xiaomingzhang12 opened this issue 2 years ago • 3 comments

Search before asking

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

What happened

  1. Choose to deploy the main branch, with the specific commit hash as follows: image

  2. Add a new Jira Cloud connection, selecting the data scope.

  3. When configuring the scope config, it is noted that the original types of issues are not present in the options.

  4. The first time, do not enter a type value, click the ❌ in the top right corner, and then click 'Add new scope config'. This will cache the content entered during the previous attempt. 20231212184056_rec_

What do you expect to happen

1。 The original types of issues can be correctly selected. 2. If the content entered for the first time is not saved by clicking 'Save', it does not need to be cached.

How to reproduce

See above

Anything else

No response

Version

main

Are you willing to submit PR?

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

Code of Conduct

xiaomingzhang12 avatar Dec 12 '23 10:12 xiaomingzhang12

img_v3_0264_64048052-70b1-4264-aca8-38a87c9eaa2g This is the phenomenon observed in the latest main branch.

  1. The status bar below cannot find the corresponding content.
  2. Clicking on the contents of the list does not select them. @mintsweet

xiaomingzhang12 avatar Dec 14 '23 12:12 xiaomingzhang12

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Feb 14 '24 00:02 github-actions[bot]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] avatar Apr 19 '24 00:04 github-actions[bot]

this issue has already been fixed.

mintsweet avatar Jun 05 '24 07:06 mintsweet