How to setup JIRA for multiple departments

[forums-5]

I apologize in advance if this is covered elsewhere.

My company has been evaluating JIRA/GreenHopper for the last month. IT was brought to my attention recently that other departments within the company would like to use JIRA as well so I am trying to determine the best way to setup JIRA for more than one department.

One thought was setting up each department as the "project" but in reading various things online this looks like it could be a limiting solution.

Another thought was to setup projects as projects and assign the category based on the department (i.e. categories would be MIS, Creative Services, etc). The concern with this however is that more than one department may have a project of the same name.

Any ideas or help would be greatly appreciated.
--
Post by cameronj - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38455
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

{quote}One thought was setting up each department as the "project" but in reading various things online this looks like it could be a limiting solution.{quote}
How about having departments in JIRA as Project Categories?  Then each project can be to a single department.  You can also name your projects (and your project keys) properly which would make them meaningful.  

Also think about JIRA's 8 schemes thoroughly as they can be a quite painful to change once you have started to create issues.  

Cheers,
Timothy
--
Post by tchin - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38455
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

I think you and Timothy are totally right about departments - set them up as categories.  However, on their own, categories aren't that useful (in V4, I think you can include category in searches in the advanced searches).  On the other hand, your users might not be that bothered - most of our users only belonged to one department, so they rarely saw anything that belonged to any of the others.

For Departments having similarly named projects though, you do have a minor problem.  Every project must have a unique key and description - we got around that by setting a standard naming convention where the project IDs and Names all had a prefix of some sort (e.g. Finance had FI as the first two characters of all their project keys, and "Finance -" on the descriptions).  

For the descriptions, you can play another trick if you need near-identical names - insert spurious spaces (e.g. The.Project and The..Project, where .s are spaces, will be rendered as "The Project")
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38455
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user