Best Practices

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

Reporting within Jira has always been its weak area. Although you can create dashboards in Jira with useful gadget and you can always rely on reporting apps like eazyBI but don't hesitate reporting outside Jira. You can always pull data from Jira and dump it to a proper reporting tool.

#jira #bestpractices

Your Jira roll out cannot be successful without good experienced project managers. That is why it is important that you spend money on hiring good PMs.

#jira #bestpractices

Required field validators are great in Jira workflows but don't forget to put those fields on a transition screens.

#JiraBestPractices #Validators

Project Managers love complicating workflows in Jira because they are not experienced or skilled. In majority of cases a simple workflow with three statuses like To Do, In Progress and Done is all you need.

#jira #bestpractices

You can move the issues in Jira from one project to another multiple times but is it a good idea?

#JiraBestPractices #MoveIssues