-
Suggestion
-
Resolution: Won't Do
-
10
-
55
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
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.
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
For Cloud instances, it comes bundled with add-ons and applications.
Some of the add-ons come with some default add-on custom fields (such as JIRA Capture, Tempo) and JIRA Software application comes with some issue types and custom fields as well, the fields are there even the instance is not licensed for the said add-ons and software. Some of the field is not editable (locked) and some of them will return after a restart.
Administrator would like to have the ability to remove the custom field in the case where they do not subscribe for the application OR even better, not to have any field or configuration deployed if the add-on is not licensed.
- is related to
-
- Gathering Interest
- relates to
-
- Gathering Interest