Ignacio Pulgar Expert

This feature is great and it was needed from long time ago! :) Regarding the notification logic, why a maximum of 5 users? I'd suggest the following logic when a user requested access this way: * Send an email to the Space Admin directly added to the Users permissions who most recently used Confluence. * Wait for 5…

Great article, @Piotr Zadrożny _Eyzee_ ! Hopefully Atlassian will develop this native feature: https://jira.atlassian.com/browse/ID-7594 If you think this would be a good addition, please vote it! :) Thank you again for providing this workaround!

Indeed! As Dan Knapton mentioned, it is key to ensure there were no spaces at all, not even after each comma!

By the way, if I had written this article today, I would have used an Automation Rule with a manual trigger. Manual triggers now can be set to include user input: A field of type Paragraph may be added to contain the comment and an Edit Issue action may add the flag. Much simpler, right?

Hi @Fawad Haq , Atlassian has changed it and now is no longer possible to display the button like in my screenshot. The Actions button now contains both looping transitions from the workflow and manually triggered automation rules, when present. I guess this provides a more uniform experience. Imagine users raising…

Hi all! Thanks for all contacts so far. @Gonchik Tsymzhitov I've sent you more details through LinkedIn. Regards

Hi @Dexter de Vera , Thanks for asking. I've just edited the post to make it clear that this position requires relocation. Thanks

Hi @PARISATO Marie-Hélène , It would consist of the same steps, except you would leave the Flagged field empty instead of typying "Impediment". Cheers

Just type "Impediment" as the value.

Hi @PARISATO Marie-Hélène , You can definitely flag an issue on transitioning an issue through a specific transition. Since you have Automation Rules at your disposal, I'd recommend going directly for that approach, as it is easier to detect all automatic behaviors in a given project, rather than having to open the edit…

Hi @Fabio Racobaldo _Catworkx_ , Thanks for the pointer! :)

Hi @Oliver Werner , Try using the email address instead of a username, and the API Token as a password. Hope it helps.

Hi @CC , Here you have one potential way for covering that requirement: * Create a custom field named Flagged by of "User Picker (single user)" type. * Create a global automation rule with the following logic:* Trigger: Field changed: select the Flagged field for all issue operations. * Condition: If-else condition* IF…

Hi @Rafael Castillo , If Story Points were meant to predict the time it may take to complete a given issue, maybe it would be better to use the Time Estimate field instead (included in the Time Tracking set of fields). That way you can go one step further and easily see which issues took more time to complete than…

Hi @Dave Mathijs , Please, correct me if I'm wrong, but the trigger issue is an Epic which lacks a value in the Epic Link field, so I think the value of Epic Link should be {{issue.key}} instead. Regards

Hi @jaspreet kaur , Here you have a screenshot on how to set it: Hope it helps.

Hi @Sarit Ashtar , That's doable through an app, as previously mentioned. If field Y were a single select field, then you can substitute fields X and Y with a custom field of type Cascading Select. Alternatively, you may just add the second field with the instructional text "(if applicable)". Regards

Hi @Umamaheswari Viswanathan , If you were using the native Versions (aka Releases), then you just need to archive a version for it to be hidden from the selectable values of the fixVersion field. Regards

Hi @Vincenzo Ciaravella , I agree with the answer by @Ste Wright. Maybe the JSD Automation does not trigger because the action of adding a participant is executed through the REST API (by an automation rule) rather than manually. Please note even the new Automation rules need to enable a checkbox on the Rule Details…

These are great news! Thank you very much! :)

Hi @Konstantin Zhabko , The way in which we cover the need for prepopulating text to be used in the Description field consists of the following: * Create a new custom field of type Paragraph (also known as Text (multiple lines)) named Form-1. (Note this field can be potentially re-used once per each Jira project in which…

Hi @Luke Hawkins , Yes, you can call API functions through the Send Web Request action in Automation. As you have already pointed out, it currently exposes the credentials in plain text, which is of course a risk. There is a feature request to avoid exposing said credentials which I invite you all to vote for:…

Hi @Erna Putri Utami , For updating previously existing issues, you may use the Schedule trigger like this: The Action would be executed on every issue returned by the JQL filter, so ensure it returns just the issues you would like to edit. Hope it helps.

Hola @Cindy Delgado , El permiso global Make Bulk Changes que mencioné en mi anterior comentario creo que es lo que necesitarías. Pruébalo y si encuentras algún problema, coméntalo por aquí y lo vemos. Un saludo

Hola @Cindy Delgado , Entiendo que necesitas dar el permiso Bulk Change. Si es así, puedes configurar qué grupos tienen el permiso Make Bulk Changes aquí: https://TU_SITIO.atlassian.net/secure/admin/GlobalPermissions!default.jspa Cambia TU_SITIO para poner la dirección que aplique en tu caso. Si quieres que todos los…

Not only that, issues can be deleted as well over time... Why would you need to hardcode issue ids? If anything, it would be better to programmatically query the issues you are interested in collecting in a different way, like looking for the presence of a label: labels = my-script Or maybe even better, depending on your…

Hi @Ana Martinez Arroyo , The answer by @David Harkins is correct. Under some circumstances, you might prefer to use a Validator rather than a Condition, especially if you can show an error message, but Conditions are generally preferable in most of the cases, since they completely hide the transition. Regards

@Mubashir paray the flag feature is only available in Jira Software boards at the moment.

Hi @John Dunkelberg , Thanks for your feedback! It is an interesting approach having AD groups with people names on them, based on who reports to who. I'm just thinking: Atlassian User Groups names cannot be edited once created... How is that solved when a user to which other people report is substituted by another person…