We are implementing both Confluence (for a Knowledge Base), and JIRA. Our consensus is that leaving labels uncontrolled in Confluence (as a KB) is OK, however, in JIRA we have concerns that they can get out of control, limiting their usefulness. We can envision using labels in saved searches. We are seeing examples of misspellings, mixed capitals already in our test system. We have concerns that labels will become a mess. Is there any benefit in restricting the ability to create labels, and is there a plug in (for server) that is helpful. Thanks. Bob
Don't put so much consideration into them. They are easily input for personal queries. As an administrator I usually keep an eye out for things that need to transition to actual fields but using labels as a quick-n-dirty way to start tracking new data is simple and easy.
Again, once it outgrows the usefulness of the labels field, transition it to controlled data.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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