I am not Admin and we have different teams using the same workflow for change request creation. I want to have default sub tasks in my change request. Is it possible to differentiate my workflow from the team.
Thank
Sruthi P
No.
Workflow is a process the issue is supposed to follow, not a process a human can arbitrarily do differently. If you need a different route through the process because you are "special", then you need to build it into the workflow (extra transitions, protected by conditions that say "only special people can use this transition")
The answer is Alexey creating a workflow with conditions that only some people can see.
Or you could use scriptrunner or automation, to create yourself a button that automatically creates the subtasks you need. You can even put conditions on who can see it, so it is not exactly in the workflow but allows you to create default things with one click.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Without admin right, then there is not much you can do. You need to have admin permissions to modify conditions and validations in the workflow.
Automation for Jira is possible to use with normal permissions, but you need an admin to install this for you.
Sorry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Building on @Nic Brough -Adaptavist- answer, 'special people' should be designated by having them assigned to specific roles. I do this so project admins and or lead developers can execute a 'won't fix' or Cancel transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is not possible, no. All users share a single workflow for an issue type/project combination.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
You can create a common workflow and then add conditions to certain transitions, so that these transitions would be visible only for certain users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is true, although building unique workflow paths based on individual user desires is not at all scalable, nor is it likely a precedent that an administrator would want to set.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.