If you copied the system workflow and you wish to rename the workflow transition buttons on the View issue page, you must delete the following properties from all transitions in the copied workflow: jira. i18n. title; jira.i18n.description; Otherwise, the default names (i.e. values of these properties) will persist. Read more about transition
Hello Claudia, You can view the link between them by Viewing the Workflow : Select a specific ticket by clicking on its ID or on its summary. On the screen, clic on "View Workflow". This will display the link between the different status and will help you understand how they work.
Raise a Change request to replace the printer, it could be in the same Jira Service Desk instance, may be different project or any other Jira Service Desk instance. Incident Problem Change. Since these these tickets are linked, the status of one can be shown at other linked issues. Once Change request is approved and resolved (printer
In the mindset of JIRA it's better to create multiple issue types and use that field to define what type of work it is and what type of workflow it requires. The issue type is meant to indicate what type of work the issue is about. A particular type of work might require a different workflow from the other. If the workflow is slightly different
Answer accepted. You can create a sub-task on workflow transition with Create on Transition for Jira. You have to perform a post function, upon issue transition, it automatically creates a sub-task for you. See the below example post function, which creates a sub-task along with information like, Issue type, Priority, Reporter and etc fields
Just my idea, by using sub-task. Create new issue type (use sub-task issue type, you can give the name for this issue type) and define simple flow contain status waiting approval, approve, reject. in parent ticket, if you need approval create sub-task from above issue type and assign to approver. if need 2 approver, create 2 subtask, if need 3
Jira Service Desk comes with templates that get you started from day 1. Let us take a look at the workflows that comes out of the box with IT Service Desk te
Tier 1 - Service Desk Team member with Service Desk License. We do total ownership were the tier 1 support representative is responsible for seeing the issue all the way through to closure. Tier 2 & 3 - Service Desk Team member with Jira License. This individual can see the issue and comment on the issue but only internally.
Each issue collects and displays the information your team needs to collaborate into a set of fields. An issue's status, priority, and resolution represent some of the most important fields describing and reporting on your team's work. They give your team at-a-glance information about where the work is in your workflow, how important it is to
kJ8Swr. 7myczii7p9.pages.dev/4407myczii7p9.pages.dev/2547myczii7p9.pages.dev/7597myczii7p9.pages.dev/9617myczii7p9.pages.dev/8457myczii7p9.pages.dev/5597myczii7p9.pages.dev/6787myczii7p9.pages.dev/5637myczii7p9.pages.dev/187myczii7p9.pages.dev/6747myczii7p9.pages.dev/9107myczii7p9.pages.dev/9677myczii7p9.pages.dev/3677myczii7p9.pages.dev/3017myczii7p9.pages.dev/100
jira service desk workflow examples
