-
Bug
-
Resolution: Fixed
-
Highest
-
7.12, 8.5.0, 8.6.0, 8.7.0
-
7.12
-
4
-
Severity 2 - Major
-
4,004
-
Summary
If we have a default resolution set in Jira, creating issues through Portfolio plans results in the new issues having 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 via Portfolio
- Commit it so that 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):
Workaround
Workaround 1
- Unset default resolution (in 'Clear defaults') in Resolutions page
- Commit
- Set the default resolution back
Workaround 2 (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
- is cloned from
-
JPOSERVER-2016 Default Resolution causes issues to be committed with Resolution Date
-
- Closed
-
- is related to
-
JRASERVER-70041 Trying to clear the Default resolution results in an XSRF security token missing page
-
- Gathering Impact
-
- resolves
-
JPOSERVER-2016 Default Resolution causes issues to be committed with Resolution Date
-
- Closed
-
- mentioned in
-
Page Loading...
- was cloned as
-
FLASH-1930 Loading...