-
Bug
-
Resolution: Timed out
-
Low
-
3
-
Severity 3 - Minor
-
Issue Summary
The fields menu in company-managed (formerly classic) projects (plugins/servlet/project-config/{projectid}/fields) displays all fields in the Default Field Configuration including team-managed (formerly next-gen) fields. This can cause inconsistencies in the display of fields on the various screens and may cause confusion to the users.
This is happening for Jira Core, Software, and JSM projects.
Steps to Reproduce
- Create a custom field in a team-managed (formerly next-gen) project.
- Navigate to a company-managed (formerly classic) project which uses the default field configuration
- Navigate to project settings → fields
- Inspect the list of fields in the default field configuration. The team-managed (formerly next-gen) field will be listed over here.
Expected Results
The team-managed (formerly next-gen) fields should not show up under the Fields configuration of company-managed (formerly classic) projects.
Actual Results
The team-managed (formerly next-gen) fields show up under the Fields configuration of company-managed (formerly classic) projects which is using Default Field Configuration.
Workaround
NA
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team