Using JIRA, all stuff are shared. for instance, name of states inside a workflow can't be the same than another state that already exist inside another workflow.
if we have 10 workflow in our server, we need to rename the state to be sure there are unique. For instance for the "open" state, I will have :
workflow1_open
workflow2_open
...
It is not very beautifull. Isn't it possible to work inside a workflow and telling the tool that this workflow don't reuse existing state from other worflow so that I could name my state with short names ? (open, close, etc...)
The same with attributes, transition, screen, etc. if the number of workflow increase the name of these stuff will need to be prefixed with the name of the workflow...
Hi Ribas,
What are you actually trying to do? There is no reason why you need more than one Open status. If want to use a status other than open, then create a new status, but don't call it some form of Open.
thanks, yes you are right, maybe for status my question is useless because status are not configurable except for their names. but for fields used in the workflow I will have the same problem...
one attribute "description" that may have rich text or not depending on the workflow where it is used...
the same for the transition that have names ? transition from "open" to "in progress" could be configured differently from one workflow to another workflow and then I may need to add the name of the workflow before the name of the transition ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can copy the workflows and modify them as needed for the transition names. You don't have to share the same workflows, though that is best for maintenance.
As for descriptions of custom fields, you can create different field configurations for each project for each issue type. In the Field Configuration you can change the Description.
You are mixing a lot of things here, so work on changing one thing at a time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @ribas
No your request is not feasible.
Why is this a concern, status are unique yes, but you can use this status in any workflow.
What is the reasoning to use prefix for example like an status called "Open"
A status is not bound to a workflow a status is an building block to be used in a workflow.
It is also best practice to re-use workflows if projects to minimise admin work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not an expert but if we did like this could it be possible that an evolution of this status in workflow1 and it will impact workflow2 (change the name ? or change anything else about this status ?)
For attributes it is more problematic. Imagine we need to have a "description" attribute. for one workflow the description is in rich text but for worflow2, "description" is not rich texte.
for transition the same, etc etc.
i'm not an expert of what could be configured in each object of jira but only for attribute, I can see there could be a problem if we reuse existing attributes.
Also having workflow1_description or description1, description2 is not very beautifull. except if it is possible to name attribute with a name then have a "display" name that is different ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.