-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.2.5.1, 6.3.2.2, 6.3.11, 7.4.1, 8.5.8
-
6.02
-
17
-
Severity 2 - Major
-
7
-
If different context is defined for the Flagged Custom Field, Jira Agile board action "Flag" doesn't work.
It doesn't work for the projects inside the new context only. For projects on the default context Flagging works fine.
Steps to reproduce:
- Go to Custom Fields: <instance>/secure/admin/ViewCustomFields.jspa
- Click on configure for field Flagged
- Add new Context and add it for just one agile project.
- Go to that project's board
- right click on an issue and select 'Add a Flag'
- Expected: Issue is flagged
- Result: Error shown
This configuration would be useful to flag issues when created for a group of projects and easily distinguish them on the board.
Workaround:
Avoid creating additional configuration context for Flagged field and reserve only one configuration context for the field for now.
- is caused by
-
JSWSERVER-14675 Lock the Flagged Custom Field used to store impediment value
- Closed
- is duplicated by
-
JSWSERVER-19882 Context Flagged custom field causes error when Flagging issue on Board
- Gathering Impact
- relates to
-
JSWSERVER-9232 Flagging issue is broken when we change the values of field options
- Gathering Impact
- mentioned in
-
Page Loading...