JIRA Software and JIRA Work Management

[Wanda Gomes Antonio]

Hi guys, 

In my company we use JIRA Software and JIRA WM together. I tried to create a project the name RAMAL in JIRA Software to control the Devs team tasks, and after that I tried create other project with the same name RAMAL in JIRA WM to control de tasks for the others teams like (production, fiel service for example). The problem is.. JIRA does'nt give the option to use the same name for both, by the way... I need to follow this project in diferent teams. Could you give me some ideias to do it the right or better way please? 

[Hana Kučerová · Accepted solution]

Hi @Wanda Gomes Antonio ,

you cannot have two projects with the same key. Why don’t you name the projects for example RAMAL SW and RAMAL WM? It will also be easier for you to distinguish between them.

[Wanda Gomes Antonio]

Hi Hana, thank you!! Hana, additionally, I have a question regarding the basic structure of JIRA usage. My manager has requested that I change our work approach. Usually, we create a new project and assign names, but now we have been asked to create teams instead of projects. According to my manager, it would be more beneficial to view teams rather than projects on the panel. Could you confirm if this is the right direction?

[Kathy Hart · Accepted solution]

I believe you will find that you can have two projects of the same name as long as they have different Keys.

But I would think you would want to have slightly different names on the projects anyway so that your users do not get confused about which one they are supposed to use. RAMAL WORK and RAMAL DEV for instance. 

Keys: RAMALW and RAMALD, or RWORK and RDEV. 

The constraints of the system are there for very good reasons. Learn to make them work for you. 

[Wanda Gomes Antonio]

Hi Kathy, I want to express my sincere gratitude for your contribution! In fact, I have previously attempted what I'm about to mention; I am just double-checking to see if there are any other possible options available. Additionally, I have a question regarding the basic structure of JIRA usage. My manager has requested that I change our work approach. Usually, we create a new project and assign names, but now we have been asked to create teams instead of projects. According to my manager, it would be more beneficial to view teams rather than projects on the panel. Could you confirm if this is the right direction?

[Kathy Hart]

Jira is based on Projects with Issues in them. You can create the Project based on the Team. Meaning, name the project for the Team, but the basic building block is still a project. 

If you are using Cloud Premium, then you can go into Plans and create Teams. These Teams can then be attached to specific projects or tickets to make planning easier. 

Jira is immensely configurable, so if you want your projects to be Team centric, then you can do this. You can pull issues from multiple projects to be under one Epic and then use the Team field to understand which team is working on which project. 

[Nayeemuddin Khan]

Create Groups (Permission) and assign Project to each group.