Dick Community Champion

Hi Dawn, It is possible to make an automation with a manual trigger that: * Checks if the (trigger)issue you invoke the automation from is of issue type Epic. * if true, generates your story and subtasks, if not you end the automation. It depends on the amount of epics in your project if you would like to do this manually…

Hi Sven, I would use components to distinguish between products and projects for each team to have work in. Issues are connected to commits in GIT repositories. So yes, if we collect multiple issues in a board, we can have multiple repositories "connected" to the board. One board per product is achieved by having the board…

There will be a small question as to provide additional info to mandatory fields in the epic

Hi Jose, Move the story. You can select the same project, but also you can select a different issuetype during a move. 

you can define your string in a variable Automation object: {{comparisondate}} = "2024-04-10" (the code for entering april 10th ^^) then convert it to a real date object with the {{comparisondate.format("yyyy-MM-dd")}} command.

best convert the object to a string with a suitable format which you choose, then match the date-string you want to compare it with in similar format. 

Hi Dailet, welcome. The stuff in quotes is a string, the smart values in your comparison are dates. you must compare apples to apples, otherwise both comparisons give a "false" result, which means the rest of the code is not executed. You would need to convert the string to a date(-object) More on entering your own dates…

Have you checked the general Layout from the general configuration menu? A small css entry to put a div or class to zero height / disabled springs to mind... :)

Why not via a transition screen between statuses?

Hi Rishabh, You can even go as far as making a manually triggered subtask automation, that will complete the copy-actions given by @Dexter de Vera if it is started from the "more" menu in a story. That will save your Jira Automation a lot of extra Automation-time, as the automation is only triggered when it is actually…

Ciao Sergio, Smart values come with double curly braces, as per this link for syntax. That might solve your issue. 

Hi Dabblu, First of all, users get a role for a given project. This means that a Jira Software user can have an administrator role in project A and a developer role in project B.

if you use the search for issues menu command, the customfield (cf_) id is visible when you enter part of the fieldname in the querie space.

if contract end is a custom field, you should lookup its ID first, then use: if {{lookupIssues.customfield_123456}} less than {{now}}(-7d)

Hi Fraser, In the if statement you're not referring to any issue at all. So it compares null to a date. you should have if {{lookupIssues.Contract End}} less than {{now}}(-7d) to include the looked-up issues in your if statement. More on the power of smart values with lookupIssues on this page

Hi Ayush, As your quest starts with a status transfer to "accepted", an automation on status change would give you the opportunity to mark the initial start date-time in a custom field. Your third party tool Time to SLA should then maybe be so smart as to monitor that custom field and check if the difference between…

Hi Nicole, As per this link, the team you want to check against needs to be a user group. Syntax is given there as well. :)

post functions in Jira are located "on" the arrows in a workflow. edit a workflow, click an arrow and you get the small window where you can i.e. set the transition screen. Also visible is the link towards the post functions.

Pardon, this works for custom fields. The ID's from the statuses are in database table IssueStatus. To list them, use Select * from dbo.issuestatus in a suitable database program. Then you'll be able to see if in your case there are multiple status ID's having the same name. @Walter Buggenhout is also touching an important…

best go with the ID's of the statuses. you can get the ID of statuses if you perform an issue search and start the query with: status = In the popup list beneath you see the status names and their cf_xxxx values. Use those to copy over values between your two types of project.

Hi, I'm not a fan of keeping a double administration in a single database. Isn't there a way to avoid this whole synchronization agony by using a single project with i.e. a well-defined component to discern whether something is MAFSI or AFSIM or both? 

Hi Nicky, It depends a bit how your teams are organized. If your teams each have a Jira Project, it would look something like: project = "Team A" or assignee = currentUser()

Boards and Projects often get confused, no worries

According to documentation on regex and Jira, you needn't escape the curved brackets:: Regex validation | Atlassian Support | Atlassian Documentation

Hi Max, Use parent link = [key of your initiative, ie XYZ-10] to get the children of your initiative. 

Hi Mark, As I'm on Datacenter Jira, it might be a bit different, but are you sure that the actor of the rule has the permissions needed for making the clone? Normally, when I make a rule, Jira sets myself as the actor. In all cases, we use a different (bot) actor to distinguish the resulting change from that made by a real…

Syntax is elaborated with examples at: Using Assets Query Language (AQL) syntax | Jira Service Management Cloud | Atlassian Support

Not my forte, but isn't the IN supposed to be followed by an array (brackets) with objects? project = "Secondline Customer Service" AND problem IN ("CS-99") 

A nice read to get up to speed with math in Jira: Jira smart values - math expressions | Cloud automation Cloud | Atlassian Support

You can have permissions in spades, but if the sprint items are not completely done (including the sub-tasks), you're not allowed to stop the sprint. This is by design.