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.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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