nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Naming conventions on JIRA when supporting multiple departments

Jason Plumhoff

After the success of JIRA in our software group, I've been asked to set up projects for other (very different) departments. This will require me to create different statuses, workflows, permission schemes, etc.

Can anyone who has done something similar share what naming schemes they used to keep it all straight? I'm worried that as I add custom fields and statuses, I will start confusing which items get used with which departments. I could make something up, but I'd really like to hear examples that have been tested in the real world...

Thanks,

Jason

Accepted answers

Renjith Pillai

Generally the schemes, workflows contain the project name to identify what it belongs to.
Custom fields try to reuse as much a possible. Set the contexts to the valid projects to avoid confusion while searching.
Status is tricky part, again attempt maximum reuse across projects, but this is bound to cause some confusion.

All comments

Renjith Pillai

Generally the schemes, workflows contain the project name to identify what it belongs to.
Custom fields try to reuse as much a possible. Set the contexts to the valid projects to avoid confusion while searching.
Status is tricky part, again attempt maximum reuse across projects, but this is bound to cause some confusion.

Jason Plumhoff

Thanks Renjith, that was pretty much what I had thought. For status, I tried to reuse as many as possible, but I still have to create a few. I've gone with adding a 4-letter prefix representing the department that "owns" that status to the name. It seems like it will keep things clean enough for me to track it. Schemes are going to be a problem for me even if I get the naming right. I have to confess, I always struggle with how schemes work. Just one of those concepts I can't quite ever seem to internalize... Jason

Renjith Pillai

Status with a 4 letter prefix of the department can actually prevent re-use. Once a department is used to that name, they will fight against changing it if someone else asks for the same status. Also there is a big role to play in educating people that slight changes in the status wordings can help a lot in keeping the instance clean and easy for maintenance.

Hanae alahcen

is it possible to have a custom field for a specifical issue ?

for example in a merketing project if an operator needs to know about the target i want him to create an issue to ask for the target we propose for him then i want specificly for this issu a field names ( target )

may i explain all this in frensh ?

because i really need an answear !

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration