Best Practices

Don't involve too many people in your discussions for configuring Jira.

#JiraBestPractices #KeyStakeholders

Always created these two screens in your Jira instance.

#JiraBestPractices #CommentScreen #ResolveScreen

Custom field context has multiple benefits. Not only it will help you have different options based on projects but you can also ensure that the field is hidden in other projects even with the shared issue type screen schemes.

#JiraBestPractices #CustomFieldContext

Are you wondering whether you need one or two admins?

#JiraConsultation #Admins

Don't think that doing small changes in Jira won't do any harm.

#JiraBestPractices #ChangeControl

New project creation should be a well defined process in your organisation. This will ensure users have thought about what kind of work they want to manage and it will encourage them to use standard Jira configurations.

#Jira #BestPractices

Have you thought about creating a Sprint called Under Discussion? This could be an open sprint with no dates and you can keep all your issue where discussion is happening in this sprint. This will always stay in sight in your backlog.

#Jira #SprintUnderDiscussion

It is a big pain to convince all the teams to follow and use the same global hierarchy.

#advancedroadmaps #Hierarchy

You might want to reorder the Issue Links that appear on the Issue screen by renaming the issue link type name but doing that will break the filters. So don't do it.

#JiraBestPractices #RenameIssueLinkTypeName

You need to be honest and often blunt about your approach but be nice and respectful to others.

#jira #bestpractices