Project Setup Best Practices

I've been using JIRA for years now but recently changed jobs and inherited a bunch of existing projects that were all created as one-offs. I want to reorganize all the configs and eliminate the duplicates but what I've come to realize staring at all the scheme spaghetti is that there are quite a few ways to achieve the same end. Before I start getting everything aligned, I wanted to ask the internet how they like to do it and why.

For example, I have a bunch of custom fields defined some of which are set to specific projects and issue types. Other issue types are set to global and their behavior is defined in field configuration schemes. My instinct is to set all of them to global and fix the necessary FC schemes. What gotchas am I missing of I do that?

How do you handle a bunch (over 20) of similar but not quite the same projects? Where do you start the setup process? Where do you define what? What are your best practices?



2 answers

If you delete any filed - you need to check on - WF's (condition / validation / Post function) , then Groovy scripts if you have any and then the impact of filed on dashboards

trying to be a good Answers citizen!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,562 views 15 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you