Our JIRA cloud instance has become somewhat overgrown by customization and we are working to streamline our way back to some common configurations. For example, we have more than 10 due date fields now and I can see a need for two or three. We also see alot of configuration schemes, some of which are related to inactive boards; perhaps the unused configurations can be discarded.
What are best practices for JIRA Cloud? We notice that the default system fields are hard to detect. While we might like to use them, since they do not jump out visually, it is makes it more difficult to suggest best practices to end users.
There are many best practices for managing configurations inside of Jira! This document from Atlassian outlines some of the best practices one should consider specifically when looking at custom fields.
When you say that the default fields do not "jump out" visually, what are you referring to?
Thanks,
Kian
Hi Kian, typically I see s/w providers highlighting default fields either with certain colors or fonts or another differentiator. In our current scenario, using JIRA Cloud we cannot determine the default fields - it's very odd and apparently a known issue in JIRA Cloud that Atlassian shows the custom fields but not the default ones. So "Due date" is the system default but there is no way to know that. The initial cap is missing on the second d so that also makes it seem like it is custom field that was not properly typed. ;-) We have had 60% of our users converge around using "Original Due Date" which is custom field someone added at some time because they did not know that the JIRA cloud system default was in fact "Due date".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have a link for JIRA Cloud ? It looks like the linked content is for Data Center.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The concepts of governance/field management apply to both deployments of Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.