-
Suggestion
-
Resolution: Unresolved
-
5
-
13
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
This is a periodical update on this suggestion. As always, we thank you for raising and voting on this suggestion. We have reviewed this change and we will not be able to implement this feature at this stage. We know that this is important to you and will keep this in "Gathering interest" as we look into improving the management of custom fields, and will be providing updates as we progress.
We also have an available workaround that could help with this in the meantime:
Going to the following URL will return all your saved filters as JSON:
https://<your site name>.atlassian.net/rest/api/3/filter/search?expand=jql
If you are about to change the name of a custom field and want to make sure it is not referred to by name in an existing saved filter, you can search that JSON response to make sure. Please let me know if you have any questions!
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Carol Low
clow@atlassian.com
Product Manager, Jira Cloud
I understand that JRA-38795 has rejected automatically updating filters when a custom field is renamed.
However if the query is stored as a string it would be possible to search these strings for any that contain the name of the custom field.
This data could then be displayed to the administrator on the 'confirmation screen'.
Displaying the ID/name of the filters and the name of the owner would give the administrator a chance to pro-actively notify the owners of the filters that they will need to update their filters.
- is related to
-
JRASERVER-61048 As a jira admin asked to rename a custom field, I want to know which filters contain the custom field, so I know which ones to update
- Gathering Interest
- relates to
-
AUTO-468 Support for field IDs instead of just field names in Automation, so rules don't break when fields are renamed, and to support custom fields with the same name
- Gathering Interest
- was cloned as
-
JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name
- Closed
- mentioned in
-
Page Loading...