-
Bug
-
Resolution: Duplicate
-
High
-
16
-
Minor
-
13
-
Issue Summary
If you create a custom field in a team-managed (formerly next-gen) Project and the name already exists in the company-managed (formerly classic) global custom fields, using the field in a JQL search will break, causing any existing filters using this field to fail.
Steps to Reproduce
- Load the existing filter which has the custom field as part of JQL Or create a custom field in the Company Managed Project and save it as a filter.
- Create a custom field in the Team Managed Project with exact name of the field in the Company Managed Project.
- Open or reload the saved filter created in step 1.
Expected Results
The JQL basic and advanced search should recognise these are 2 different fields and continue to function accordingly.
Actual Results
All the existing filters will break that has this custom field with below error:
Workaround
- Delete the custom field that's created in the Team Managed Project Or,
- Simply rename one of the custom fields so there are no duplicates.
- duplicates
-
-
- Long Term Backlog
-
- is related to
-
-
- Closed
-
-
JRACLOUD-79983 [Tracking in issue links] Various issues related to actions that cause broken Saved Filters
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[JRACLOUD-79845] Saved filter for the JQL breaks with when user create the same custom field name in Team Managed Project as of Company Managed Project.
We started using Team managed projects when we went to Cloud because it seemed like such a good solution to our thousands of users and hundreds of projects to not have every one of them need to work with the admins to make changes.
That was until a team managed project admin added a field they wanted for their team, and all of the bug tracking filters and automations for our main corporate engineering project broke, causing mass chaos and lost time while the Eng project admins and our entire DevOps team scrambled to append "[Value]" to the end of the existing custom field of the same name to dozens of filters and boards and automations....on release build day....what a mess and waste of time and money it was.
Team managed projects should simply be blocked from creating fields with duplicate names...if they REQUIRE that field then they can make a similar name, or they can work with admins to create the duplicate in a way that doesn't break everything else (can you use contextualized custom fields in Team managed projects?)
We basically cannot use Team managed projects now, and may have to take over ownership of the existing ones to keep this from happening again.
The same happened with a new field named "Sprint" created by a non-admin who is not aware of the impact
need a warning for such cases
Similar mitigation as -> https://jira.atlassian.com/browse/JRACLOUD-79586?focusedId=3318824&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3318824
—
As a mitigation for this issue we've introduced new validation which will allow the user to identify when a query fails due to duplicated field names, and suggests alternate terms to correct their query.
The user can update their filter with the suggested JQL term to resolve the error and prevent and future validation errors due to duplicate field names.
Thank you all for your patience.
Kind regards,
Kyle & Yousef