Rule execution on issue sending smart values from version

[Suporte JRetail]

Hi,

So I have 2 projects, one where the issue is created and another for the developers where the version is created. When a version is created in project DESENV we send an e-mail that creates an issue on project AJ, is there a way to create a rule that sends a slack message with smart values from the version? I need the version name, description and items on the version.

If there is a way to link the issue to the version it would be great too, because in that way I could create ramification rule to get the version smart values I need.

NOTE: The issue created has the version name in it.

[Bill Sheboy]

Hi @Suporte JRetail 

Yes, most of what you ask may be implemented with automation rules, although there may be differences from what you mean.

First, issues are normally linked to versions with the Fix Version and / or Affected Versions fields.  Versions are specific to one project, and so the versions in your development project could be assigned to the issues in that project.  This could be done manually or using a rule, depending upon the triggering criteria.

Next, automation rules can send Slack messages: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-Slack-message

You may want to send a message when the version is created, or for other version activity.  Please look here to learn the smart values available for the version-related triggers: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--version--

Finally, as the versions are by project, you could not link your one project's issues to the versions in another.  There may be alternatives, such as linking the issues instead to access the version data.  I recommend writing down an example of what this would look like, with issues and versions in the projects, and using that to decide how to proceed.

Kind regards,
Bill

[Suporte JRetail]

Hi @Bill Sheboy 

Thanks for the information, so I have an example, here is how it's done in our Jira, 

The version has Items linked to it.

And the issue is created so another team can upload the changes to the server, example:

So it is not linked, and when I tried linking it, by clicking in "Link Item" I couldn't find the version key.

Now about the rule, it would be triggered by the issue and not the version, and then it would send a message in slack (The slack part is already done), but I can't seem to use smart values from the version when the issue is the trigger.

The solution would either link the version to the issue, or get the version data directly through the rule, that has issue as the trigger.

Regards,

Suporte JRetail

[Bill Sheboy]

When the issue is the trigger, please reference the field the version is assigned to and then use the smart values.  For example, if the version is assigned to the Fix Versions field, it could be this:

{{issue.fixVersions.last.name}} to be released on {{issue.fixVersions.last.releaseDate.jiraDate}}

Seeing the specifics of your entire rule will help to clarify this.

Also please note well: there can be multiple values in the Fix Version field, so I noted last to access that one.  If you plan for issues to be in multiple versions, some adjustments will be needed.

[Suporte JRetail]

So right now the version isn't assigned to any field on the issue, how can I do that?

So the entire rule would be, when an custom field (Analista) is changed the rule is triggered, than I have 2 if's for other 2 custom fields: Analista and Módulo. Then it sends an message on slack.

[Bill Sheboy]

Let's clarify the scenario as I do not understand the order things are happening for your manual steps versus what you want to automate.

Please describe the steps of the scenario, from beginning to end, including...

• when versions are created
• when issues are created
• when should the version be assigned to an issue (that is, the triggering event)
• which version should be assigned to a issue
• when should a Slack message be sent
• what information the Slack message includes
• etc.

I recommend pausing to explain the problem you are trying to solve and the complete steps to one of your teammates first.  Doing so will help confirm your understanding of the situation before trying to automate any steps.

[Suporte JRetail]

Sorry for the confusion, that's how it is happening right now:

1. Version is created

2. Issue is created

3. Version is uploaded to the server

4. I manually send a slack message warning that the version was uploaded and leave a comment to register that the version is up and running

5. then the team check for errors

6. the version goes to production server

The steps 6 and 3 are written as a comment on the issue.