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...
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.
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 !
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...
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!
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