Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

On this page

Table of Contents
maxLevel2
stylecircle
typeflat
separatorpipe

UI Text Box
sizemedium
typeinfo

Use case

For the annual access review of applications used within in the company , and managed as Jira Service Management Assets, we would like want to create a dedicated task for each application owner to review the people having who have access to the application they are respinsoble responsible for. 

UI Text Box
colorlight-yellow
icontip

Prerequisite

You are using Jira Service Management to manage the applications used within in your company. For this use case, the asset scheme where the Asset schema in which your applications are organized is referred to as the CMDB. Here, your applications are classified with the object type "Application" and include at least one custom attribute, "Application Owner," which is configured and set.

Configuration steps

UI Steps
UI Step

Get started

To create tickets for every application in our asset database, we utilize the "Create Issue" post function. As we would like to generate a dedicated ticket for each application identified in the database, we configure the Mode* parameter to "Multiple issues based on a text list" and use the getAssetsFromAQL() expression parser function to return all asset keys as a list. The elements of this this can later be used via the %{seed.text} field code.

Mode

:

*

Multiple issues based on a text list

Expression*

Code Block
%{getAssetsFromAQL("objectSchema=CMDB AND objectType=Application")}

UI Step

Setting the project and issue type context 

Select an Issue Type and Project that best suit your needs using the accoring issue type and project parameter. Ensure that the chosen Issue Type is available within the selected Project.



UI Step
GIve

Give the tickets a summary

Since we’re generating multiple tickets, we want to differentiate them by including the application name directly in each ticket summary. To do this, we use an expression that dynamically inserts the name of the application for which each ticket is being created. We achieve this by using a field code with the getNameFromAsset()parser function, which converts the asset key from the %{seed.text} field code into the application’s name.

Code Block
titleSummary*
Annual review of %{getNameFromAsset(%{seed.text})}
Tip

You can enrich the summary with more information. For example, you might add the current year by including i.e the year() function in an expression like this:

Code Block
Annual review %{year({system.currentDateTime}, RUN_AS_LOCAL)} of %{getNameFromAsset(%{seed.text})}
UI Step

Getting the work done

Creating the ticket is just the first step. To ensure proper attention, we want to assign the application owner as the ticket's assignee, making them directly responsible for it.

To set the assignee to the to be created issue, click on Add Field and choose Assignee.

To assign the application owner, we need to retrieve their information from the asset database using the %{getAttributeFromAsset() expression parser function. We then set the Assignee field of the issue to be created with this data, ensuring the owner is directly responsible for the ticket.

Code Block
titleValue*
%{getAttributeFromAsset( %{seed.text}, "Application Owner")}
 

Related Examples

Page properties report
firstcolumnUse case
headingsJWT feature, Workflow function, Parser functions, Complexity
sortByTitle
cqllabel = "use-case" and space = currentSpace() and ancestor = "38569502"

Page properties
hiddentrue


JWT feature

Workflow function

Create issue

Parser functions

getNameFromAsset()

getAttributeFromAsset()

getAssetsFromAQL()

Label
Use case descriptionFor the annual access review of software used within the company and managed in Assets, the functionality automatically creates a ticket for each asset in a scheme. The new ticket's assignee is set based on the application owner of the asset. 
Complexity

Status
colourYellow
titleINTERMEDIATE



Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue