-
Suggestion
-
Resolution: Fixed
-
None
-
None
COS:
- Rename any existing instances of the field to Epic Name
- Rename the type of the field to Epic Name
- Ignore any change items that were previously created against this field
- Search for any references to "Epic Label" and replace them with "Epic Name" – including documentation (cc: rosie@atlassian.com)
Testing Notes
Q: What if there is a duplicate named field?
A: This could cause unexpected results but miruflin states we can't do much about this. Deemed unlikely and an extreme edge case.
Q: What if there is a field type for this already in the system?
A: This could cause unexpected results but miruflin states we can't do much about this. Deemed unlikely and an extreme edge case.
Q: What about existing quick filters or swimlanes (any JQL) that reference the field name?
A: JQL will become invalid, same as any JQL made on a field where the name is changed. Swimlanes/QF would be using Epic Link though since the parent's value is not available.
- is related to
-
JSWSERVER-6678 in 6.1: "Epic Label" will be renamed to "Epic Name"
- Closed
- mentioned in
-
Wiki Page Loading...