Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,368,141
Community Members
 
Community Events
168
Community Groups

Using Labels as Project classification

Hi all,

 

I wanted to ask, if it makes sense to classify Projects via Labels in Jira ?

e.g.:

Project 1 as Label "Project-1"

Project 2 as Label "Project-2"

We are using a Team Managed Project and there are no components, so we are thinking about using Labels to classify the different projects within one Board. Does it make sense also with regards to create reports?

 

Thanks in advance!

3 answers

Thank you for your answers! Since I'm the only person who creates the lables as projects, there should not be any problems that someone selects a wrong label, right? Since we only use one team managed project board, all issues have the same issue key, so it would not be possible to find the project via the key! And in a team managed board you can not create multiple projects as such.  So I see no other option than using labels to classify.

Hi @Lena Kook ,

In your specific case, labels do seem like the most viable option. Personally, I would prefer to use a dropdown field, but either should work.

If I am not totally mistaken, label-based filtering is enabled automatically on team-managed boards, so you don't need to configure any filters.

Best regards,
 Oliver

Like Lena Kook likes this

Hi @Lena Kook ,

It's possible, yes. But like @Nic Brough _Adaptavist_ says, it does not make much sense, as you can get that information from the issue key. I say this as one of the biggest fans of the label feature.

However, just for completeness' sake: If you only have one team managed project in Jira, but need the issues in that single project to represent various real-life projects, then labels might make sense. Still though, I would prefer a Dropdown field, as you can specify the valid options, instead of having to rely on everyone to spell the projects correctly.

Hope that helps,
 Oliver

0 votes

You can identify the project of an issue by looking at the issue's key or by searching on the project field.   Boards can even do swimlanes by project.  A label or component would be redundant, just making extra work for people who would have to remember to populate it.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events