Fernando Eugênio da Silva Community Champion

@Jennifer Sousa , bem vinda à comunidade Atlassian. Por serem projetos com recursos mais limitados, os projetos do tipo team-managed não possuem o Sprint Report. Entretanto você pode usar o Sprint Burndown Chart para ter no team-managed uma visão similar que você teria usando o Sprint Report no company-managed. Basta você…

@Reynalda Torres , You only can do this using Jira Software Cloud Premium, with this resource you can manipulate the Issue Type Hierarchy and configure the Issue Type levels as you want. Read a litle more: https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/…

@Kevin Baidas , Welcome to the Atlassian Community You need to change the scope of your automation rule to something similar to this one: I tested it in the format I am sending you and it worked fine. If you succeed like this, the form will be properly copied. Regards, Fernando - Atlassian Consultant | OAT Solutions

@Alex K , Please, try to use this: {{triggerIssue.summary}} It works! Regards, Fernando

@Sree Vinayak Balasubramaniam , welcome to the Atlassian Community! If you're using Jira Cloud, try using the REST API GET for JSM Cloud itself: https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-requesttype/#api- rest-servicedeskapi-requesttype-get If, as you indicated, you have permissions on the…

@Fredy Alexander Pena you can use like this: status IN (cerrados, abiertos) (Use this to display a list of items in one of these statuses.) Or you can use this: status = cerrados (Use this to display issues only in closed statuses) status = abiertos (Use this to display issues only in Open statuses) See…

@Marc Kraak You can use these groups in custom fields like "Group Picker". By default, Jira already has a field like this called "Approver groups". This field can contain several groups at the same time. You just need to define the approver group in this field and define this field as source for the approval step of your…

@Landon Tran , You can add more information in this notification such as Description or Summary. To do this, do the following: Go to Project Settings > Customer Notifications > You will see an "Approval Required" notification, click to edit it. Then you will see the notification template, you can customize the text and…

@Chris McCullough Great!! I would say to you change "name" to "value", it's because custom field select list (multiple choices) are different than "Components" field in jira. Glad to hear you made it lol Any questions, let us know best

@Thiago Constantino , bem vindo à comunidade Atlassian. Com as informações que você deu ainda não é possível entender o que você exatamente precisa. Você consegue compartilhar mais detalhes sobre a sua dúvida? Atenciosamente, Fernando

@Thiago Constantino , bem vindo à comunidade Atlassian. Você pode fazer isso usando o operador lógico IN em sua query no jira. Exemplo: project IN ("TI", "DP") Dessa forma o Jira irá trazer resultados de issues de ambos os projetos. Veja mais…

@Hassan Rachid Yes, I saw it. Honestly I had some difficulty until I understand that the PUT method is only accepting "Edit Issue" not related to status/transition or maybe I didn't understand the payload right The method I got was sending a POST payload like I showed you before. Maybe it's a case for you to see with…

@Hassan Rachid If the event does not ask for field changes, just forward the issue. You must use the following parameters. Metodo: POST URL: https://your_site_name/rest/api/3/issue/{{issue key}}/transitions Payload: { "transition": { "id": "XX" } }

@Hassan Rachid , Welcome to the Atlassian Community! You can only edit fields in a transition event via REST API, if this transition has an associated screen. This is because the transition event will edit the fields and status together. If you intend to transition the issue and edit fields without an associated screen in…

@Jaroslav Jasek . Welcome to the Atlassian Community A good idea for this is to use Jira Service Management using Assets. Assets is an asset management tool where you can create various schemas for users, departments, equipment and properties in general. It's currently a free, built-in feature only for Jira Service…

@[deleted] , Check the jira URL. The content after HTTPS:// is your jira cloud instance.

@[deleted] Can you confirm if the SVR project is a Service Management project? If yes, maybe theuser doesn't have an active license of the "Service Management" product? If the automation error indicates that the user does not have permission, then maybe he is not a licensed user for Service Management, where the SVR…

@Juliane Assis , O jeito mais fácil de obter este resultado é usando uma ferramenta como o EazyBI. Além de fornecer várias possibilidades de relatórios, no EazyBI você conseguirá ter esse dado de uma forma visual bem melhor. De qualquer modo, é possível você ter uma contagem de quantas vezes a issue passou por determinado…

@Genival Neves Brasil Junior , So far, no payload errors have been pointed out. The error indicates that the ID field 12302 is not being displayed in the issue. Have you tried putting this field to be displayed in the issue? Make sure it's on the "Edit" and "View" screens. Then try again and see if the error still persists.

@Sreenadh By default, Description field doesn't accept a default value. This is possible in one of two ways: 1> Create a custom field of type "paragraph" and define the default value for it. Make the whole configuration of assigning the field on the issuetype "Incident" screen and then you can by automation copy the value…

@Raymart Cruz Yes, it is possible. But you will need to use some product to synchronize this data, like Atlassian Access. Maybe in the marketplace there is an add-on that makes this possible too, but for a more complete solution, Atlassian Access should do just fine.

@Adriana.Agudelo Puedes usar una consulta similar a esta: project = XXXX AND "Epic Link" = "XXXX" Por lo tanto, solo traerá problemas del proyecto A asociados con Epico del proyecto B Si no funciona, describa con más detalle qué es exactamente lo que está tratando de obtener como resultado. Fernando

If you are using subtask in your JSM project, the field that will be filled in jira to map the Story is the "Parent" field. Subtasks cannot be linked to an issue via the "Parent Link" field. So it is not possible for you to see this data in the "Parent link" field or in the "Links" field.

@Suzi Firth This isn't a bug, it's standard Jira behavior. The "Parent Link" field is used to map issue levels a little above Epic. For example: From Initiative to Epic > Parent Link (Levels higher than Epic it's available only to premium/enterprise plans) From Epic to Story > Epic Link From Story to Subtask > Parent…

@Vivian Nogueira , bem vinda à comunidade Atlassian! Atualmente não é possível ter essa estrutura copiada para um campo customizado do jira. O campo "Prioridade" é um campo do tipo 'System Level', que possui algumas particularidades bem específicas, como esta identificação por cor. Você pode adicionar novas opções ao campo…

@Sergio SPOT Puoi farlo usando il trigger Pianificazione dell'automazione. In Schedule puoi pianificare l'esecuzione delle regole di automazione in base a una query jira. Vedi l'esempio di base: Questa automazione verrà eseguita ogni giorno alle 9:00 solo per problemi di progetto in cui il campo Data di inizio è lo stesso…

In this case, I would recommend that you create a second issuetype for this relationship, if that's really necessary. Changing the hierarchy is global and will affect all other projects/plans where the "Initiative" issuetype is being used. If you create a second issue type and put it on the same level as Epic it will serve…

@David Mitchell Welcome to the Atlassian Community. To do this, you need to put the issue type "Initiative" at the same level as Epic in jira. Access the global jira settings and go to the "Issue type hierarchy" option. On this screen, add the "Initiative" issuetype in the same location as Epic. As this is a different…

@alexander.cartlidge Glad to know that it worked for you! If you don't have the "Approval Completed" trigger on your automation, then you can use the "Issue Transitioned" event to execute your rule. Considering that when Manager 1 approves, jira will transition the Issue to another status, I believe this trigger will help…

@alexander.cartlidge , this is working for me { "update": { "approvers" : [ { "remove": { "id":"user_id" } } ] } } Can you try this in your automation rule and share the screenshot of your audit log automation? If you could share your complete automation rule, I think can help us to understand better your rule structure.…