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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event