nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA automation to create dynamic filters and to edit the filter permissions

Abhishek Kalamkar

Hi All,

I want to create a dynamic filter as soon as Version is created. Based on the version values, like version name and version description, need to create a dynamic filter and save it as version description name. once done, need to edit the filter permissions. can you please help on this. here is the screenshot of what i am doing.

Accepted answers

Jehan Bhathena

Hi @Abhishek Kalamkar

As @John Funk rightly mentioned this cannot be achieved out of the box, since the {{version}} is limited to provide only the version name and version ID.

In theory you can do this as a workaround :

Use the Below webrequest to fetch the newly created versions

Note: the Delay further requests option is important for the next steps
Use the details received from the above webrequest as input to another Webrequest, namely:
{{webResponse.body.description}} and {{webResponse.body.name}}
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-post

You might need to do some trial and error with the create Filter API since the input may not be in the specified format needed.

Do let us know how it goes.

PS: would recommend Hidding the Auth token in your image

All comments

John Funk

Hi Abhishek - Sorry, but you will not be able to do any of those things with an Automation rule.

Jehan Bhathena

Hi @Abhishek Kalamkar

As @John Funk rightly mentioned this cannot be achieved out of the box, since the {{version}} is limited to provide only the version name and version ID.

In theory you can do this as a workaround :

Use the Below webrequest to fetch the newly created versions

Note: the Delay further requests option is important for the next steps
Use the details received from the above webrequest as input to another Webrequest, namely:
{{webResponse.body.description}} and {{webResponse.body.name}}
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-post

You might need to do some trial and error with the create Filter API since the input may not be in the specified format needed.

Do let us know how it goes.

PS: would recommend Hidding the Auth token in your image

Bill Sheboy

HI @Abhishek Kalamkar

Adding onto the answers already provided...you note wanting to name your new, saved filter using the just-created version's description.

What information are you putting into the version description?

It is possible that your description contains text which cannot be saved as a filter name, so please keep that in mind when creating this rule. Some work-arounds could be to remove/replace any characters in the description which are not permitted in saved, filter names, or to instead use the version name.

Kind regards,
Bill

Abhishek Kalamkar

Thank you @John Funk

John Funk

You are welcome.

Abhishek Kalamkar

@Jehan Bhathena Thank you for your answer. below is working for me as it is only the text value. As you mentioned, I only need the {{version.name}} value should be name field and JQL should use JQL: "to use smart value"

"name": "{{version.name}}" --> Filter name should save as value of {{version.name}}. filter name should save as CWC 9.5

This is what I have tried but no luck.

@Bill Sheboy : Thank you for your input. I don't really care about the description. If possible, I would like to have version description or version name same as above screenshot which is CWC 9.5

Jehan Bhathena

Hi @Abhishek Kalamkar ,

As shown in your image

This webrequest should work (in theory), do you get any error? What is not working in this use case now?

Also, as a request please use the individual thread for responding to each response, so that we have a more clear line of reasoning. :-)

Abhishek Kalamkar

@Jehan Bhathena : please find the error. I have tried multiple ways, it will allow only text value but not {{version.name}} or {{webResponse.body.description}}

When I try for Get, custom data - that works fine for me as it retrieves all the filters data.

Jehan Bhathena

@Abhishek Kalamkar , you cannot validate a request that uses a smart value.

For {{webResponse.body.description}} to be resolved the first Webrequest needs to be fired, once done, the next request will use the output from the first request in the body.

As of now, you're trying to send a empty value in your request that is why you receive the error "name has to be provided".

Would recommend triggering the automation and let the whole automation run and see if it works.

Let us knw how it goes.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud