For each major release we need to create couple of generic Epics (for packaging, documentation, maintenance, etc). I'm looking for automation as I think it is the best solution and I'm facing couple of difficulties.
Preliminary information:
The rule I created for now (which doesn't work) is as follow:
Now my questions:
Anybody to help?
Hi @chm
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
For the regular expression, you seem to have some variability for the naming. Perhaps try using the digit matcher \d for your patterns, and specifically look for "- Release" at the end.
For the epic, {{version.name}} should work for the Summary, but to set the Fix Version instead use the id with {{version.id}}
Kind regards,
Bill
Hi @Bill Sheboy
I thought the pictures would not add any valuable info therefore I didn't send that. However no problem to share them. Please find below the automation rule:
Note: I modified the pattern and this one seems to work pretty well for my need, so only my second problem remains (epic creation).
The details of the Epic creation is like
As you see it is a very simple rule for now (I'll complexify step by step). Just create an Epic in the given project - VRE (I tried "in same project but it didn't change anything) and just set the summary and the fix version.
I set {{version.id}} as you suggested but it didn't help. At least I don't know if it improves or not since the error message is of no help for me.
Here we see the first (below) trial were I gave a different name than Release to check if the naming pattern was working and it seems it is ok.
Then I made another trial with the right name (upper) and the rule passes to the next step which is Epic creation. But then "some error" happened.
I don't know if I can trigger some more debug information.
Thanks for your support
Christophe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for my mistake, as when I just tested an example rule, I found that the name must be used to set the fix version in the issue create: {{version.name}}
Please try that and let me know what you observe.
Also...Are you trying to create an issue in the same project where the version is created, or in a different project? I tested in the same project, with a project-scope rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I tried also with {{version.name}} but it doesn't change.
I tried using the "same project" option for the Epic creation but then I get a complain about it not being defined.
I would have preferred this generic option to deploy it as a global rule but I can handle it as local rule, not an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just tested this scenario as a global-scope rule and it worked for me, with a specific project selected and "project from trigger" (which would automatically select the project for the version).
Let's try to narrow down some possible impacts...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill
I went to check every single point you listed and it triggered something in my brain... Here are the answer and the solution.
After running all the verifications above I started to believe I was doing the right thing (since it works for you) but I must have forgotten a basic thing. So I created a new rule which is "manual trigger --> create an Epic". No smart value, nothing fancy. As simple as that. This simple rule failed as well. Then I realized (how dumb I am and) that in our template, we have couple of mandatory fields at creation time. Once I added all those fields to the rule and set proper values, my simple rule worked.
I did the same changes to the initial rule which is triggered from version creation and I got my Epic issue created, with the correct title and the correct fix version.
I'll now be able to complexify step by step the rule to get the most out of it (I already faced the next issue but I'll dig it out).
Thank you very much for your good support Bill.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well done diagnosing that!
That is a curious, and unhelpful error in the log for the required field. When others have encountered that scenario a different error can appear for this in the audit log. My hypothesis is this error depends upon the type of field which was required.
I checked the public backlog for any suggestions for this and did not find one, so consider adding one here: https://jira.atlassian.com/secure/Dashboard.jspa I am currently on a free license and so can no longer add suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @chm
Can you tell what is your requirement to create Epic.
Should the newly created Version have "-.Release" in it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Kalyan Sattaluri
Thanks for your quick support
my requirement is when a version is created, if its name matches the pattern, then couple of EPICS must be created. The Epics should get the version name in their summary, plus some addition to give the topic of the Epic. The fixversion should also be set with the version name.
Yes as of today our process is to have "- Release" in it as we use the releases also for intermediate milestones (if Atlassian release the milestones in Advance Roadmap we may change our process but they didn't comment on the request lately).
I think I found a working pattern with "ProductName.*Release".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.