Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

Versions Compared

Old Version 13

changes.mady.by.user Rebecca Plattner

Saved on

compared with

New Version 14

changes.mady.by.user Rebecca Plattner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
UI Text Box
sizemedium
typeinfo

Use case

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

UI Text Box
colorlight-yellow
icontip

Prerequisite

You use Jira Service Management to manage the applications used in your organisation. For this use case, the asset schema in which your applications are organised is called the CMDB. Here, your applications are classified with the object type 'Application' and have at least one custom attribute, 'Application Owner', which is configured and set.

Configuration steps

UI Steps
UI Step

Get started

To create tickets for each application in our asset database, we utilize the Create Issue post function. As we want to create a separate ticket for each application identified in the database, we configure the Mode* parameter to "Multiple issues based on a text list" and use thegetAssetsFromAQL() 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.

Code Block
titleMode -> Multiple issues based on a text list -> Expression*
%{getAssetsFromAQL("objectSchema=CMDB AND objectType=Application")}

UI Step

Setting the project and issue type context 

Select an Issue Type and Project that best suits your needs using the appropriate Issue Type and Project parameters. Ensure that the selected Issue Type is available within the selected Project.



UI Step

Give the tickets a summary

Since we're creating 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

Assign the ticket to the application owner

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

To set the assignee to the to be created issue, click on Add Field and choose Assignee. There we are setting the value of the field based on a parser expression.

To assign the application owner, we can 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
titleAdd field -> Assignee -> Set field value manually (parser expression)*
%{getAttributeFromAsset( %{seed.text}, "Application Owner")}
 

Image Modified 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 applications used in the company and managed as Jira Service Management Assets, we want to create a dedicated task for each application owner to review the people who have access to the application they are responsible for. 
Complexity

Status
colourYellow
titleINTERMEDIATE


Excerpt Include
DECADIS:Contact support
DECADIS:Contact support
nopaneltrue