Best Practices

It is great that Jira can be integrated with other tools using REST API but you should always monitor the usage of these integrations because too many integrations can cause performance issues.

#jira #bestpractice

You should regularly monitor the usage of various apps in your instances and get rid of the apps that are not needed. Saving money is also your responsibility.

#jira #bestpractice

It is not possible to change custom field type in Jira but you can always create a new custom field with the same name and migrate the data.

#bestpractice #jira

Don't try to make your Jira instance perfect, focus on the outcome and delivery not the tools you are using.

#bestpractice #jira

Not many Jira admins utilise the security schemes in Jira to hide certain issues from users.

#bestpractice #jira

It is a good idea to ensure that new project created in Jira is hidden by default and only people added to that project can access it.

#bestpractice #jira

People often use Custom Fields to further elaborate their Statuses in the workflow and I think it is okay but don't overdo it.

#Jira #BestPractices

I know it is crucial to have up to date documentation of your Jira configurations but it also painful to keep it up to date. A lot of time and resources can go into maintaining documents.

#JiraBestPractices #Documentation

Statuses and Resolutions are two different things. Many Jira Admins don't even use Resolutions.

#JiraBestPractices #Statuses #Resolutions

When Jira Admins use their own final state, they often forget to add a Post Function to Fire an Issue Resolved Event. This is important so that any listener can act upon and do something when issues are resolved.

#JiraBestPractices #IssueResolvedEvent