Sam Harding Atlassian Team

Comments

  • Hi, I think a possible solution here would be to add a custom field to your Issues. You can add a 'Number Field' as a custom field, call it a name like 'Retest Count', then in Automation for Jira, you can have it set up to: 1. Trigger on 'Issue Transitioned' from 'Testing' to 'Retest' 2. 'Edit Issue', fields to set:…
  • Hi, This is possible to do, as the smart values supports regular expressions on its Strings. I believe the correct syntax for doing what you want is the following: {{issue.XXX.match("(\[.*?\])").get(0)}} The matching regex here will return a list of all strings which are between a [ and ]. The results will include the…
  • Hi Justin, At this point in time, Automation for Jira does not support interaction with confluence, so you cannot achieve this using Automation for Jira alone. Perhaps you could direct this question to other community spaces, such as Script Runner for Confluence, and see if others have achieved what you are wanting to do.
  • Hi Bryan, from the screenshot above, it looks like the rule does not have the 'Lookup Issues' component in its component chain. The Lookup Issues action only defines the {{lookupIssues}} smart value for the Automation rule it is added to, so every rule which wants to use the {{lookupIssues}} smart value must have the…
  • Yes, summing up story points is one of the most desired use cases for this feature. We have a number of fields/properties we will be adding to this shortly, with sum up story points being one of the first that will be rolled out.
  • Hi, Automation for Jira provides an action 'Add Service Desk Customer'. It may be possible to perform this operation by having a rule trigger on 'Issue created', and then running the 'Add Service Desk Customer' action, using smart values to fill out the users email by using '{{issue.reporter.emailAddress}}'. Let us know if…