Organization in Atlassian

[Chris Rainey]

Hey everyone,

I am currently preparing to transition my organization from another tool to Jira Service Management. We currently use Jira (JSW and JWM) so I'm wanting to get ahead of potential confusion surrounding organization. I know it's very easy to overengineer in Jira and don't want to end up with that headache. I dealt with that in a past organization and will do my absolute best to prevent us from going down the same path.

The reason I'm posting here is to get an understanding of how folks in the community use things like naming conventions to keep things organized. Some questions:

• How granular do you get with your naming conventions?
• What items do you apply naming conventions to? Projects? Screens? Workflows? Etc.
• How are projects organized for you? Do you take advantage of project categories? Do you use a naming convention for projects?

Thank you all in advance - I'm very eager to work on this transition for us and your input here will be extremely valuable for me.

[Rick Westbrock]

If I modify any out of box JSM objects like workflows, screens, schemes etc. I make a copy and prepend a four character acronym (our company abbreviation) so it's very clear to other admins that the object has been customized. This also allows us to easily revert to the default object later if needed.