-
Suggestion
-
Resolution: Won't Do
-
3
-
13
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact us if you have any questions or feedback.
Regards,
Michał Tomasik
Software Engineer, Jira Cloud
When we save a filter that includes a custom field, Jira should save the field based on its id rather than the name of the filter.
For now, if we rename a field, it will break all the Filters, Automation Rule when the Field is in use.
How this is going to benefit us:
1. Saving a filter using the filed name, if we rename the field, we get the error - "Field 'alpha' does not exist or you do not have permission to view it."
2. If we use, field ID -> example cf[10131] is not empty , this continues to work even if we rename the field.
- is cloned from
-
- Gathering Interest
- is related to
-
JRACLOUD-83050 Duplicate Custom Field Names in Team Managed Project is causing issues with JQL results
-
- Closed
-
-
- Gathering Interest
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
[JRACLOUD-76466] Jira should store the custom field details based on field ID instead of the field name
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact us if you have any questions or feedback.
Regards,
Michał Tomasik
Software Engineer, Jira Cloud
All comments
Just noting here that you can save a filter that refers to a custom filter by its ID rather than its name. If you do this, the saved filter will not be broken if you change the custom field's name.
To find all your custom fields' IDs, go to https://<your site name>.atlassian.net/rest/api/3/field
In the following example the id of my custom field is 10098:
To use it in a filter's JQL you need to type cf[10098]
After changing the custom field's name, the saved filter referring to the field's ID continued to work:
Whereas the custom field that referred to the field name has broken:
Pinned by
Michał Tomasik
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact us if you have any questions or feedback.
Regards,
Michał Tomasik
Software Engineer, Jira Cloud