Hi there,
we have created a done-status named 'archived' in a shared workflow for epics (used by several projects). How can I make this status available only for selected projects that use this shared workflow?
It should not be visible for the projects its not supposed for as this would confuse the users there.
Thanks in advance
Hi @Harald Heinz ,
My suggestion here is, create a copy of the workflow and then remove the status you don't want to be shown in some of the projects.
Later associate this new workflow (with removed status) with a new workflow scheme and then to the projects you don't want the status to show up.
Hope this helps.
Regards,
Anzar Khan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Feel free to accept the answer ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Harald Heinz
If your workflow is simplified workflow (meaning you can jump to a status from any status) then simply create a condition on the workflow status to exclude it in some projects.
If its not, then you will need to adjust it so people wont get stuck and then add the condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was my first guess too, but what's the right condition for that transition then?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Harald Heinz
use "Value Field"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @arielei . Although it is no field, I can choose project there and it works. Wouldn't have guessed to find the solution there by this condition's name
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
when you create a status in company managed project it's global that is it can be shared with other project as well, if you want to create status only limited to specific project. I would suggest go with team-managed project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We use this workflow for many company managed projects and thats fine. The thing is I need the described status only to be useable within certain projects using that shared workflow.
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.