-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
8.20.0
-
8.2
-
4
-
Severity 2 - Major
-
0
-
Issue Summary
If you have multiple Target date fields (besides the 2 added by Portfolio) and restrict their context to a specific Project/Issue Type, Jira Portfolio won't commit changes to the Target date fields.
Steps to Reproduce
- Create a custom Target Start Date field
- Restrict new field's context to only 1 Issue Type
- Make changes to the Target Start field (Default field) on your Portfolio plan
- Commit changes
Expected Results
New date is committed
Actual Results
Portfolio doesn't throw any error and refreshes the date back to the original value before the change on step 3.
Workaround
Set the custom field's context to all issue types
- links to
Form Name |
---|
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC