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; } } }

Automation for Version creation

Michael Smith_snkpb5

Hello All,

I'm struggling a little. I've tried to create a new version each time a version is released. The new version is simply named the date of the release (bi-weekly in this case).

Can anyone tell me what I've done wrong here that when a version is released a new version is not created?

Accepted answers

Trudy P Claspill

Hello @Michael Smith

What information is available in the rule Audit Log for when the rule has executed?

All comments

Trudy P Claspill

Hello @Michael Smith

What information is available in the rule Audit Log for when the rule has executed?

Michael Smith_snkpb5

The trigger event is version released, however when I release a version it isn't executing so no log, I'm guessing I must need some value here?

We only ever have one release at a time and we've been using the format "mm.dd.yy" but because I didn't see a way to mimic that I just used the ".jiraDate" format not sure that really matters but in case it helps with identifying with what I should be doing for this section of the rule so it will get triggered properly.

Trudy P Claspill

So, in the rule Audit Log page you see only entries with a status of "config changed"? There are not any other entries wither other statuses?

Is the rule enabled?

What is the scope of your rule? Generally rules are associated with a single project and that is specified on the Rule Details page. Is the project in the Create Version action the same one on the Rule Details page?

Is the Version you Released associated with the Project specified on the Rule Details page?

Michael Smith_snkpb5

Hi Trudy,

Yes that's correct only the "config changed" records are in the log.

Yes the rule is enabled.

The scope is for our Project "Test Data Management (TDM)" and the scope is set the same in both the Rule details page and the create version action.

I don't see anywhere to define that project scope for the trigger unless I somehow need to point to it in that "Version Name Filter" field?

For what its worth, maybe the issue lies with how the versions are being released? I have a rule setup that closes the next version (also only version) at 4:30 PM every other Wednesday. Maybe I should try to execute the close version and create version from the same rule rather than from a separate rule Rule Details.png

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