-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
6.7.11
-
6.07
-
8
-
Severity 2 - Major
-
1
-
Problem
Flagging an issue does not work in JIRA Agile if Custom Field configuration is modified
Steps to reproduce
- Edit 'Flagged' field and change the Field Searcher to 'None'
- Re-index
Actual Results
- Flagging issues does not work
Expected Results
- Flagging works as normal
Original description
From a user : "I tested the flagging feature and it worked nicely "out of the box". I then customized the list of option values for the custom 'Flagged' field (changed wording on "Impediments" to "Impeded" and added "Priority") and re-indexed. Now, I can add a flag in Plan mode through right-click but issues no longer display with the flag icon or the yellow color, and right-click options no longer display the "Remove Flag" option, only the "Add Flag option (although the flag has already been added)."
- is related to
-
-
- Gathering Impact
-
-
JSWSERVER-14675 Lock the Flagged Custom Field used to store impediment value
- Closed
- relates to
-
-
- Gathering Impact
-
[JSWSERVER-9232] Flagging issue is broken when we change the values of field options
| Component/s | New: Issue - Fields [ 59919 ] |
| Support reference count | Original: 7 | New: 8 |
| Support reference count | Original: 6 | New: 7 |
| UIS | Original: 2 | New: 1 |
| UIS | Original: 0 | New: 2 |
| Support reference count | Original: 5 | New: 6 |
| Support reference count | Original: 4 | New: 5 |
| UIS | Original: 1 | New: 0 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |