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?
Thanks!
-Kathy
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
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.