Automation for Version creation

[Michael Smith]

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?

[Trudy Claspill · Accepted solution]

Hello @Michael Smith 

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

[Michael Smith]

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 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]

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

[Michael Smith]

@Trudy Claspill I've tried adding the create version as an additional step in my rule to release a version and its working as expected now. Thank you for your responsiveness to my request for assistance. We can call this closed :-)

[Trudy Claspill]

Just to follow up, based on the images you provided the Create Version was set to create the version in the ETT project, not the TDM project.

Since the rule trigger is the Release of a Version, it would only be triggered when a version is released from the project specified in the Rule Details page.

If you want to debug this more I would ask for a screen image of the Rule' Details page and a screen image of the version you released showing the project to which it belongs.

Also I caught that you said you used a rule to release the version. In that case you would need to ensure that this rule has the box checked on the Rule Details page for allow this rule to be triggered by actions that occur in another rule.