Details
Description
Update 6 Aug 2020:
This bug has been backported to Jira Core 8.5, will be available in the Jira 8.5.8 release.
This bug is resolved by upgrading to Jira Core 8.8, relevant ticket: JRASERVER-70656
Summary
If we have default resolution set in JIRA, committing issues though live plans causes the new tickets created in the process to have a Resolution Date, though no Resolution.
Steps to Reproduce
- Create a project
- Create a Portfolio plan and add the project as an issue source
- Go to Resolutions page in JIRA (type g+g >> resolutions, under https://instance.atlassian.net/secure/admin/ViewResolutions.jspa)
- Select a resolution as default
- Add an issue to the plan
- Commit it so it's created in JIRA
Expected Results
The ticket is created without Resolution Date, as it doesn't have a resolution.
Actual Results
It's created with no Resolution (as expected), but with a Resolution Date (not expected):
Workarounds
Workaround 1: no default resolution
Don't make use of default resolution until you can upgrade to a fixed version.
Clearing the default resolution on the Resolutions admin page's blocked by JRASERVER-70041, so to clear it you may:
- Create a new Resolution temporarily
- Set this new Resolution to be default
- Delete the new Resolution
Workaround 2: tweak the workflows (suggested in comments below)
- Change the 'Create' transition for this issue
- Add a post-function to clear the 'resolution' (not resolution date)
- This should also clean the resolution date
Workaround 3: create issues in Jira
- Create issues directly through Jira, rather than Portfolio. This should avoid the problem.
Attachments
Issue Links
- duplicates
-
JSWCLOUD-19192 Issues created in Portfolio have resolution dates set at creation
-
- Closed
-
- is cloned from
-
-
- Closed
-
- is resolved by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- is caused by
-
FLASH-1930 Loading...
- is cloned by
-