-
Bug
-
Resolution: Duplicate
-
High
-
None
-
Severity 3 - Minor
-
Summary
If we have default resolution set in JIRA, committing issues through 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):
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
- duplicates
-
JSWCLOUD-19192 Issues created in Portfolio have resolution dates set at creation
- Closed
- relates to
-
JRASERVER-40428 Issues created via IssueService with default values have Resolution Date set
- Closed
- was cloned as
-
JPOSERVER-2016 Default Resolution causes issues to be committed with Resolution Date
- Closed