-
Suggestion
-
Resolution: Won't Fix
-
0
-
2
-
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 me if you have any questions or feedback.
Regards,
Ahmud
Product Manager-Issue View
User Story
As a Jira administrator, I need archiving of a team-managed project to also hide it's custom fields from the rest of the system because we need to keep this data for historical purposes but cannot continue with the custom field dumpster fire this creates.
Context
- Project admins can create their own custom fields in team managed projects without restriction on name or uniqueness.
- Human languages have a finite number of terms for the same concept, leading to multiple TMP-sourced custom fields with the exact same name in the system.
- When looking at custom fields, Jira will in most situations simply show you the name without any other context.
- Archiving a TMP does not hide custom fields from the rest of the system.
- It is not possible to delete Jira projects if you need to retain the issues inside them for historical purposes.
This comes together to create another usability dumpster fire with very little recourse.
- mentioned in
-
Page Loading...