Ignacio Pulgar Expert

You are welcome! 😃

Hi @[deleted] , That's also native behaviour: Please, note that if the user added to the Request Participants field clicks on the Turn off this request's notifications link, they will stop receiving notifications. Hope it helps.

In the meanwhile, may you add screenshots of your Automation rule components?

Oh, a Team-Managed project, I see. I should try to reproduce it before being able to answer here.

Hi @[deleted] , That's the native behaviour. When you add a new person to Request Participants field, they receive an email like this one: Best regards

Hi @Gowri Kumar , May you check if Priority is in the screen associated to the Sub-task's create and edit issue operations? Regards

Again, listen @Nic Brough -Adaptavist- 's wise tip ;)

Hi @Sara Garcia , I agree with @Nic Brough -Adaptavist- . In order to bulk change the issue type of sub-tasks to stories, and then add the appropriate Epic Link, you may follow these steps: * Execute a query like: parent = <parent issue key> * Bulk change the issues returned to add to all of them a new label like: EPIC-123…

Hi @Christie Smith , Besides what has already been said, there's also the native structure of issues: * Epic * Any other standard issue types other than Epic * Sub-task issue types Regards

You are welcome! :)

Hi @Gavin Klose , Some checks that may help: * The Product field should be present in the screen associated with the Create issue operation of the Feature issue type. * Ensure the Feature issue type is within the scope of Product custom field context. Hope it helps. Regards

¿Puedes probar el campo Time Spent?

Hi @Trena Norcia , Maybe no Resolution is being set in the transition to the Resolved status in the underlying workflow. If Resolved is a final status in the workflow (instead of Closed), it should be provided with a Resolution through one of this alternative methods: * add a post-function of type Update Issue Field >…

Hola @Selene Riofrio Santiago , Entiendo que el campo que buscas es Original Estimate. Un saludo

Hola @Juan Portero , Si te refieres a capturar el agente de primer nivel que estuvo en el campo Assignee, sí, es posible copiar el valor en otro campo personalizado de tipo User Picker. Como parece que es algo a realizar durante un escalado, creo probable que la necesidad de capturar el agente de primer nivel aparezca en…

Hi @Михаил Кисельников , You may find this function useful: fixVersion in unreleasedVersions() If you want to have a list with the names of unreleased versions, you may save that as a filter and use it to feed a Pie Chart gadget based in the fixVersions field. Hope it helps. Regards

Hi @Kautilya Fadia IN , The format has worked for me in tests with higher numbers. Maybe you can use a Text field (single line) to avoid number format issues. Regards

Hi @Kautilya Fadia IN , When and how exactly does that format fail? If format doesn't have a consistent behaviour, then I'd consider using a custom field of type Text (single line) instead of Number type. Regards

In other words, you need to create a Work Management project to count with the Forms feature:

Hi @Srinivas Sarma , The Forms feature is available only for Jira Cloud Business projects:

You're welcome! :) Thanks for confirming it worked. Regards

Hi @Kautilya Fadia IN , You may change the number format in the smart value like this: {{issue.Customfield A.format("###")}} More info in the docs. Hope it helps. Regards

Hi @James Wardle , Try adding the Value Field condition as a third condition to the "All of the following conditions" set. With these parameters: Hope it helps. Regards

Thanks @Marco Brundel , I have not tested this rule myself, so follow this tip, @Kathryn Westwood . Regards

Hi @Kathryn Westwood , I'd say the trigger should be like this, substituting those Summary, Description and Assignee with the three custom fields you would like to concatenate: Then you may add this action: The field to set would be "Value Due Month" and this is the samrt value to copy: {{issue.Estimated Project Value…

Oh, then I misunderstood it :)

Hi @Robin Stemmers , One Jira issue may have multiple comments, so I assume you would like to store the email address of the user who last added a comment to the issue, in a custom field possibly named Email. I copy here the smart value so that you can copy it easily: {{issue.comments.last.author.emailAddress}} Hope it…

That would be a good feature, as Project Admins currently lack the ability to know which users have access to their projects through a group.

Hi @Denis Uschapivsky , Priority Schemes are not available on Cloud. The workaround would consist of creating a new custom field of type single-select named "Priority Level" (important not to name it Priority, to avoid confusion) and create a different context for each of your Service Management projects. However, I would…

Hi @Sean Lin , Maybe there's a quick filter selected in your board (?). Regards