What are some examples of good and bad Components — especially compared to Labels?

I struggle with the documentation comparing Components and Labels. It would be helpful to have good and bad examples of Components so that I can better make that comparison and understand when and why to use each.

1 answer

1 vote

A good component would indicate a distinct part of what your project is for.  If you were building a computer for example, you might want components like memory, cpu, motherboard, case, power supply, graphics output and so-on.  A poor component name would be "display", because it's not a true component in hardware, it's a concept that crosses several components.  (On a raspberry Pi for example, there's an hdmi output, a minimum power requirement, a graphics processing system and some use of memory)

Labels are totally different.  They are tags to allow more arbitrary things to be looked at.  In the example above, "display" might be a good label because you can group issues together based on the label.

Let's say I have a project on developing some other kind of Facebook;

What would be some of the good examples of COMPONENTS I could have on Jira?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

415 views 0 8
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you