-
Suggestion
-
Resolution: Unresolved
-
221
-
143
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.
While we don't have any plans to introduce generic support for renaming any system field, we are very sensitive to the feedback that much of the terminology in JIRA is unfriendly to non-technical users. We're actively exploring ways to alleviate this in the future.
It's important to understand that we rarely try to implement individual features from jira.atlassian.com, but instead take a holistic look at the problem and use feedback from the comments here and a dozen other sources of customer input to solve the core problems.
Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
This also includes renaming 'Priority' to 'Severity' as some customers prefer to use severity.
- duplicates
-
JRACLOUD-76468 Rename system fields in Jira
- Closed
- is duplicated by
-
JRACLOUD-42160 Rename "Time to Resolution" field
- Closed
-
JRACLOUD-76468 Rename system fields in Jira
- Closed
- is related to
-
JRACLOUD-42160 Rename "Time to Resolution" field
- Closed
-
JRASERVER-21293 Rename any system field via the admin section
- Not Being Considered
1.
|
Rename Issue Type Field | Closed | Unassigned |