Objectives

In this section, we will amend the workflow associated with the Task issue type so that it will trigger the lookup automation to populate the stakeholders.

Open

We will add 4 post functions

1. Lookup the Data Owner with Application and update back to the triggering issue’s Data Owner

2. Lookup the Data Owner with Application and update back to the triggering issue’s Assignee

3. Lookup the System Owner with Application and update back to the triggering issue’s System Owner

4. Lookup the System Admin with Application and update back to the triggering issue’s System Admin

About the workflow

The workflow will be as follows

1. When the issue is created, it will use the Application field to lookup the stakeholders

   1. Data Owner - the person in charge of reviewing whether the person has authority to access the data in the application

   2. System Owner - the person in charge of the application

   3. System Admin - the System admin who is responsible for granting the access

2. The request will be assigned to the Data Owner for approval

3. Once the Data Owner has approved, it will be routed to the System Owner for approval

4. After the System Owner has approved, it will be assigned to the System Admin to process the request

5. When the System Admin has completed the task, the request goes to the Completed status

6. During the workflow, it is possible to cancel or reject the request

Open

Steps

1. Entering the Workflow Edit mode

1. Click on the Workflows in the Project settings' left sidebar

    

2. Click on the Pencil icon under Actions column to edit the workflow associated with the Task issue type

    

3. Click on the Diagram tab

    

4. Click on the topmost arrow pointing to the Open status

5. Click on the Post Functions link to edit the post function

2. Adding the Lookup to set the Data Owner

We will show the detailed steps for setting up the 1st post function

1. Click on the Add post function link

    

2. Select Lookup Manager: Update Issue Field and click on the Add button

3. Select Application as the Source Field(s) since we are using that field in the Service Desk request to perform the lookup

4. Select APPMAPPING project as the Lookup Project Key since it stores the mapping between the Application field and the other stakeholder user picker fields (Data Owner, System Owner, System Admin)

5. Select Application in the Search Field(s) as it is the field in the Lookup Project to be matched with the Source Field(s)

6. Select Data Owner for the Matching Field because we will use its value

7. Select Data Owner for the Destination Field because we will use the value from step 6 to update back into the Data Owner field in the triggering issue

8. Click on the Add button

    

9. The Post Function is added successfully

2. Adding the Lookup to set the Data Owner as the Assignee

Unlike Jira Server/DC, the post functions for Jira Cloud are executed asynchronously. Thus it is not possible to add a post function to copy the value of the Data Owner to the Assignee. However, it is possible to use a Lookup post function to update the Assignee directly.

1. Click on the Add post function link

    

2. Select Lookup Manager: Update Issue Field and click on the Add button

3. Select Application as the Source Field(s) since we are using that field in the Service Desk request to perform the lookup

    

4. Select APPMAPPING project as the Lookup Project Key since it stores the mapping between the Application field and the other stakeholder user picker fields (Data Owner, System Owner, System Admin)

    

5. Select Application in the Search Field(s) as it is the field in the Lookup Project to be matched with the Source Field(s)

6. Select Data Owner for the Matching Field because we will use its value

    

7. Select Assignee for the Destination Field because we will use the value from step 6 to update back into the Assignee field in the triggering issue

    

8. Click on the Add button

    

9. The Post Function is added successfully

3. Lookup the System Owner and System Admin for the Application

1. The setup for the Lookup post function for System Owner

    

2. The setup for the Lookup post function for System Admin

    

3. The list of post functions will be like this

4. Updating the workflow

1. You can add the statuses and transitions as per the workflow diagram below

2. You can delete the other existing statuses and transitions

5. Adding the approval

We need to set up the approvals so that it will transition automatically to the next state once the Data Owner has approved.

1. Click on the link of the workflow name

    

2. Click on the Diagram tab to go into diagram mode

3. Click on the Data Owner Review status

4. Click on the Configure link in the box on the right

    

5. Select the options for the fields and then click on the Create button

   1. Get approvers from field: Data Owner

   2. If approved, transition status to: Data Owner Approved

   3. If declined, transition status to: Data Owner Denied

6. When you are done, you can click on the Publish Draft link at the top to save the workflow

    

6. Try it Out

Now you can go to the Customer Portal and create a request and test out the automation you have configured

1. Go back to the Service Desk project using the top menu

    

2. Click on Raise a request

    

3. Select Application Access

4. Fill in the fields and click Send

5. Click on the issue key at the top breadcrumbs to go from the Customer Portal view to the Agent View

6. The stakeholder fields are populated on the right side

    

7. If you click on the History tab, you can see the changes updated by the Lookup Manager

The End

Give yourself a pat on the shoulder for completing this tutorial.
Now you have learnt how to set up a new project on Jira Cloud as well as the enhancing the Jira workflow.

If you have any questions or suggestions for improvement, you are welcome to submit them at our Service Desk. It is also powered by Lookup Manager for Jira Cloud.