Content
Custom filed "TAG"
Hi there,
finally I left Atlassian and now managed to install and run openproject on my NAS.
I love and we work a lot with TAGs-field in Jira. In openproject you can add a custom field, as list, so far so good.
But when we try to add a TAG into that field (Task) then nothing happens. So, I add some predefined values in that field. Now, we can use those predefined values, but ... that's not effective. Cause we will have a lot of new TAGs, even for each Task, and there is no way to define them before.
Any workaround?
Hello Don,
At the moment, you could, for example, take a look at the categories[1] as an alternative. These can be managed individually for each project. At the same time, labels will also be available in OpenProject very soon. Work on this is almost complete. You can find more details here:
Best regards,
Alexander
It's great that the tag concept is arriving in the new version, I'm trying to prepare the company's Jira users for the probable arrival of OpenProject in their tool, and it's clearly an "absence" that would have given me a hard time in terms of resistance to change.
From my 15 years of using JIRA, categories and tags are really 2 different management angles.
In Jira
Categories provide "freedom" to project managers to frame project participants in the way they "classify" tickets.
While labels offer this freedom directly to participants.
We are on 2 different scales of spontaneity.
And it's a question of focus, when I work on the ticket, that a need emerges to "classify" the element, or we have a "framed" classification scope (a tree of categories) which meets the need, then we will favor it because it already standardizes things.
Either we feel trapped in the framework and “we don’t want to tackle it right now”, because we “just want to acknowledge this need to classify”, but regain focus on what we are doing. And there is the label, a very “tolerant” classification system.
This tolerance has a cost, we take a loan, it's a loan on time saved now but to be repaid later ;).
Managing labels is much more tedious than categories, because you have to "garden" them as they come.
We know in project management, it costs less to “prepare” (plan my category tree)
We know with the agile approach, we are much more reactive to let the field choose when the question arises, especially when it was impossible in our VUCA/BANI world to predict this question.
In short, let's think about the "human" and "interaction" aspect when choosing between Label and Category.
Let's not forget the use of "namespaces"
This also makes me think of a feature idea (but I have to check if it is not already proposed), allowing you to add a label or category "field" to a form, but with a forced filter.
This allows you to have several “trees” or “networks” of tags or categories but to restrict the user to their choices.
The alternative would be to create "different" fields, each with its own tree, but again it is a question of "freedom" of configuration.
One last point, AI turns the scales upside down when I say that label management is more “heavy”. Indeed, the proper use of AI makes it possible to accelerate these stages, and therefore to offer flexibility and freedom to users at a lower cost. Let them do it, and ask the AI to put away the “storm” of real brains (those of humans with their faults and their wealth)