youngmon/atlassian-qna huggingface dataset:
Dificuldade para criar um transi??o de tarefas entre abas
Asked by Ramon Efeito Madeira:

Estou tentando criar um percurso de produtividade dentro da empresa utilizando o JIRA, porem estou tendo dificuldade na hora de criar automa??o desse itens.  
Gostaria de ai criar uma nova tarefa que outras sub tarefas sejam criadas automaticamente, essa etapa consegui em primeiro momento, na sequencia ao concluir essas sub tarefas gostaria que a tarefa muda para a aba seguinte automaticamente e que ao mudar seja criada outras sub tarefas e ao finalizar que passe adiante, ate conseguir finalizar toda a linha de produ??o.  
Consegui fazer dois desses passos, porem na terceira aba ao finalizar as sub tarefas ao inv?s de ir para a proximo aba ele se manteve na mesma aba e criou outras sub tarefas , esse processo continuou se repetindo.

Se algu?m puder me indicar v?deos tutoriais de como me ajudar, agrade?o.


Answers:
author: Andr? Felipe Rodrigues Lopes
body: Ol? [@Ramon Efeito Madeira](/t5/user/viewprofilepage/user-id/5557764)   
Posso compartilhar um passo a passo que pode te ajudar  

Aqui est?o os passos para garantir que a tarefa progrida corretamente:  

* **Cria??o Inicial da Tarefa e Subtarefas:**

  * Configure uma regra de automa??o para criar as subtarefas quando a tarefa principal for criada.
  * Use a condi??o "Issue Created" como disparador.
  * Adicione a a??o "Create Issue" para criar as subtarefas.
* **Mover Tarefa Principal ao Concluir Subtarefas:**

  * Configure uma regra de automa??o para mover a tarefa principal quando todas as subtarefas forem conclu?das.
  * Use o disparador "Issue Transitioned" e defina para quando uma subtask ? movida para "Done".
  * Adicione uma condi??o para verificar se todas as subtarefas est?o em "Done".
  * Adicione a a??o "Transition Issue" para mover a tarefa principal para a pr?xima coluna.
* **Cria??o de Novas Subtarefas na Nova Coluna:**

  * Configure uma regra de automa??o que crie novas subtarefas quando a tarefa principal ? movida para a nova coluna.
  * Use o disparador "Issue Transitioned" e defina para quando a tarefa principal ? movida para a nova coluna.
  * Adicione a a??o "Create Issue" para criar as novas subtarefas.
* **Evitar Ciclo Infinito:**

  * Certifique-se de que as condi??es est?o corretamente configuradas para evitar que as automa??es sejam disparadas repetidamente.
  * Adicione condi??es para verificar o status das subtarefas antes de criar novas.  

    Espero ter ajudado.


Tags: cloud

jira-cloud
No me llega el codigo al mail corporativo de Jira no puedo INGRESAR
Asked by josefinamercado1987:

No me llega el codigo al mail corporativo de Jira no puedo INGRESAR

MAIL CORPORATIVO AL CUAL NO LE LLEGA EL CODIGO PARA INGRESAR ES:

**\<email_removed_for_privacy\>**


Answers:
author: josefinamercado1987
body: NO ME LLEGA El c?digo de verificaci?n por lo que no puedo ingresar por favor AYUDA.


author: Theodora Boudale
body: Hi [@josefinamercado1987](/t5/user/viewprofilepage/user-id/5557765),

The email address you shared used to be in our suppression list, there were a few bounce events when we attempted to send earlier emails. However, I see in our email logs that the most recent emails have been successfully delivered. Could you please let me know if the issue is resolved?

Kind regards,  
Theodora


Tags: bitbucket

bitbucket-cloud

cloud
Jira Assets attribute object reference multi select
Asked by Michael Frade:

In Jira Assets, if you have an attribute that is a reference to another object, is there a way to have multi select. So if the attribute is a linked to an employee object schema and you want to be able to associate multiple employees for that attribute as like a POC, is that possible?


Answers:
author: Mikael Sandberg
body: Yes, that is possible. What you need to do is set the cardinality to unlimited, similar to what I have done for the attribute catalog:

![Screenshot 2024-07-31 at 12.11.01?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/339231i254E4DB584B987A4/image-dimensions/442x236?v=v2 "Screenshot 2024-07-31 at 12.11.01?PM.png")

comments: author: Michael Frade
body: I went round and round. Thank you!


Tags: assets

cloud

jira-cloud
How can customers "Share with" their organization without emailing all other users in the org?
Asked by Jason:

When clients create tickets, we tell them to leave the "Share with" defaulted to their organization. We have to make our clients do this so that we can maintain proper reporting for tickets created at the organization.

However, by doing so Jira sends an email to every single user in that organization saying 'so-and-so created a ticket.'

We have received many complaints over the years that people do not want everyone at their company to be notified whenever a ticket is created. This inundates other users' inboxes with things that they do not need to be bothered with. We even have to constantly re-add the organization to the ticket because the client will manually remove the org from the list of "Shared with" requested participants in the client portal.

Is there a way to make it so that when someone creates a ticket they can share the ticket with the org without it notifying everyone?

Thank you!


Answers:
author: Samuel Gatica
body: Hi [@Jason](/t5/user/viewprofilepage/user-id/4164770)

If you want to allow customers to share with their organization without automatically emailing all other users, you can consider the following options:

* Navigate to **Project Settings** \> **Customer Notifications**
* Find the notification rule for "Customer-visible status changes" and "Organization added "

![Screenshot_4.png](https://community.atlassian.com/t5/image/serverpage/image-id/339253i6BCB0F1A4C453F25/image-size/large?v=v2&px=999 "Screenshot_4.png")

This implies that when a customer reports an issue within their organization, an email notification will not be automatically sent to all members of the organization.

Please note that other actions, such as comments to the client, will also notify the customers involved.

Hope this helps

Best regards

Sam

comments: author: Jason
body: Thank you so much! We will play with this setting to see if this resolves the issue.

As a follow-up, do you know if there is a way to make this the ruleset for all clients except for a specific few? We have one major client that does like to see when tickets are created because they operate with their own separate support team that triages their company's tickets before sending them to us so when they create a ticket they all want to be aware. I am guessing there is not, but no harm in asking. Thanks again!

Edit: We figured out a plausible workaround using automations and made it so that the necessary parties are emailed whenever a new ticket is created for their organization and they are not listed as the reporter. :)


Tags: cloud

jira-cloud
Status Order
Asked by Andrew O_Connell:

How do I get the statuses to appear in the same order as I have them in my workflow? It appears they're in alphabetical order.


Answers:
author: Mikael Sandberg
body: Hi [@Andrew O_Connell](/t5/user/viewprofilepage/user-id/5557707),

Welcome to Atlassian Community!

Have a look at this [KB](https://confluence.atlassian.com/jirakb/changing-the-order-sorting-of-workflow-status-transition-button-on-the-issue-view-page-1267663718.html) on how to change the order. Basically what you do is add the **opsbar-sequence** property to each transition and give it a number. It is recommended that you start with 0 and then increase it by 10 for each transition. This would allow you to add new statuses/transitions and sort them without having to change the number on all of the transitions.


Tags: cloud

jira-cloud

jira-cloud-administration

not-applicable
Update dates based on dependencies
Asked by Katie Joskowitz:

A = original blocking issue

B = blocked by A

C = blocked by B

I set up an automation so that the start/end dates of a dependent issue (B) are updated when the actual completion date of the blocking issue (A) is updated. However, when I run the automation, the issue immediately linked to the blocker (B) updates, but none of the issues blocked by issue B update. Is there a way to ensure that when A is updated, it will change B and since B is being updated it will update C and so on?

![Screenshot 2024-07-31 at 10.11.22?AM.png](/t5/image/serverpage/image-id/339209i51AD5122D6E1FA93/image-size/large?v=v2&px=999 "Screenshot 2024-07-31 at 10.11.22?AM.png")


Answers:
author: Shawn Doyle - ReleaseTEAM
body: It looks like this automation runs when A changes, so the automation knows of A and can go through it's linked issues to update B. It doesn't know of B's linked issues, so can not update them.

A few ways to approach this;

1. You would need this automation to load all of B's linked issues and update them, most likely in a branch.

2. Create a separate automation for when B issues changes to update the linked issues.

3. Make the current automation trigger smarter to catch both A date changes OR B date changes to update their linked issues.


Tags: data-center

jira-data-center
automate submit jira ticket
Asked by Sampath:

Team

In Jira we can do

automate submit jira ticket

pls suggest


Answers:
author: shib saha
body: Hi [@Sampath](/t5/user/viewprofilepage/user-id/3886406) , Yes, you can take help of Jira automation to create Jira ticket automatically. But what is the requirement like on certain day you want certain jira tickets to be created or on completion of some activity in the project you want some Jira ticket to be created?

Please post the complete requirement word by word and we will help you with setting up the automation rule. Thanks

comments: author: Sampath
body: Hi [@shib saha](/t5/user/viewprofilepage/user-id/4610701)

Thanks for your response.

Plan to have it

- When user facing issue instead of goto link or send mail for creating ticket its there any BOT option that can be available in JIRA to submit the ticket instead of create


Tags: cloud

jira-server
Article Question: Upcoming changes: 'epic-link' replaced with 'parent'
Asked by Catherine.Moody:

In this article: [Upcoming changes: 'epic-link' replaced with 'parent'](https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/) the image

![Jira Parents.png](/t5/image/serverpage/image-id/339182i6AA7D4A34D8A64A3/image-size/large?v=v2&px=999 "Jira Parents.png")

implies that initiatives can have a parent. Is this something that needs to be configured to allow this to happen?

Catherine


Answers:
author: Hans Polder
body: [@Catherine.Moody](/t5/user/viewprofilepage/user-id/5394625) ,

Yes, the hierarchy can be customized as much as you want. You can contact your product admin to evaluate this (as it will have impact). See this article for more information: <https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/>

comments: author: Catherine.Moody
body: Thanks for the quick follow up Hans. I will investigate futher!!


Tags: cloud

jira-cloud

jira-software
Move a ticket to reject status , currently in close status.
Asked by Randeep Kaur:

Need help to move to reject status, currently in Close status. Also the workflow for this project has no listed Reject bucket. Is there a possible way to update work-flow and move this Jira ticket to reject status?![JIra.PNG](/t5/image/serverpage/image-id/339191i26829AD62AFD9365/image-size/large?v=v2&px=999 "JIra.PNG")


Answers:
author: Dave Mathijs
body: Hi [@Randeep Kaur](/t5/user/viewprofilepage/user-id/5370638) Unpopular opinion: Leave the 'CLOSE' status as it is and add a Resolution 'Rejected' to your list of resolutions. Then create a 'Resolution' transition/workflow screen with at least 'Resolution' as field and choose 'Rejected' as resolution when transitioning to the 'Done' status.

PS: The name of the status would better be named CLOSED (status) instead of CLOSE (action/transition name).


author: Bhanu
body: Hi [@Randeep Kaur](/t5/user/viewprofilepage/user-id/5370638)

You can add the Reject status and a Transition to move it to the Reject Status.

Be cautious when you do this, If you are on a Team-Managed project, this should be fine, but if you are doing it on a Company-Managed project, you will need to check if the Workflow scheme is shared with other projects and make the change only for the projects on which you want the change applied to.


Tags: cloud

jira-cloud
Suggestions for a Pre-Resolved Status
Asked by Guy Renko:

For recent requests, we'd prefer if customers add a comment to the previously resolved request however some (all) customers have trouble remembering how to view "Closed" requests in the customer portal.

We're hoping we can set a pre-Resolved status for requests that may require a confirmation or a grace period so customers still see the Request as open but we're not sure what it should be named or even if it should be a "To Do" Status Category or an "In Progress" Status Category.

We've set the pre-Resolved status, currently named "Testing", to pause the SLA and an Automation to transition to Resolved if the request has no comments in X days.

I tried to set direct transitions between statuses, but everyone kept asking for a way to move to additional statuses so now most of the statuses have a global transition, but they are conditional. No statuses show during the Waiting for Approval status and only Reopen shows when the ticket is Resolved/Canceled and I set the ops-sequence properties to show some coherent order or statuses in the Request dropdown.

![24-0731 IT_ Request Workflow 2024-0730.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/339168i9E9D07120BD03A6D/image-size/large?v=v2&px=999 "24-0731 IT_ Request Workflow 2024-0730.jpg")

Hoping for some suggestions on what to call this pre-Resolved status, currently named "Testing", and if there are any other settings we should consider.


Answers:
author: Joe Pitt
body: It looks like you want the customers to comment on the issue.

What are you going to do if it is a negative comment? Will you reopen it? If it's a positive comment you can then resolve and close the issue.

If that is the case you I suggest you create two transitions:

one, Named Customer Accepts and have a field 'Customer Comment' that is required that sets the resolution and closes the issue, and

two, Named Customer Doesn't Accept, and require the same Customer Comment' field and have it reopen the issue.

comments: author: Guy Renko
body: Thank you for the suggestion but I don't suspect that customers will let us know if anything is working fine. Only if something is not working.   

I even set this Testing status to automatically transition to Resolved if there are no updates (comments or field changes) to the Request for three days.   

Definately though not loving "Testing".

In Review?

Finalizing?

Complete?


Tags: cloud

jira-service-management

jira-service-management-cloud
How can i disable comments in portal after 5 day of closing
Asked by Annalaura Di Nunno:

Hi community,

I would like to disable comments in the service desk after 5 day of closing.

I found some possible solutions when the status is closed (Property : jira.permission.comment.denied = true) but this property disables comments permanently.

I need your support.

Thanks

Annalaura


Answers:
author: Victor Law
body: Hi [@Annalaura Di Nunno](/t5/user/viewprofilepage/user-id/1057182)

I would suggest having two different workflow statuses for similar requirements:

* **Resolved -** Customers/users can still comment after this ticket is marked as resolved
* **Closed -** Customers/users will no longer be able to comment or edit this ticket by setting the following properties in the workflow status properties:
  * jira.issue.editable = false

  * jira.permission.comment.denied = true

You can also set up an automation to transition any ticket from **Resolved** to **Closed** if there is no update after 5 days in the **Resolved** status.

Thank you.


Tags: data-center

jira-data-center

jira-service-management

jira-service-management-server

server
Field Configurations - Required Fields
Asked by Orla Mears:

Hi all,  

Literally pulling my hair out here, I have looked at all levels of material and info but not getting my issue resolved.  

I have a project which is currently using an existing field configuration, which has some fields marked as required.  

I created a new field configuration and scheme, then went to the project in question and then I go to:  

Project\>Project Settings

Fields\>Actions Wheel/Cog

Edit Fields\>Associate an issue type with a field configuration  

However, this then changes the field configuration for every project that has this issue type associated!  

I created the Field Configuration and scheme so I could remove the "required" flag on a field, but it's not working and I'm past trying to figure it out.


Answers:
author: shib saha
body: Hi [@Orla Mears](/t5/user/viewprofilepage/user-id/5499710) , What i suspect is you have added the field configured in the same field configuration scheme which is shared with multiple project.

Solution: Copy the existing field configuration scheme and also the field configuration, now the associate the copied field configuration to the copied field configuration scheme. Now make those fields optional which is required.

And this way the field will become optional only for your project and rest of the project won't be affected.

I hope it will be helpful for you. Thanks


Tags: cloud

jira-cloud
Assign another workflow to "All Unassigned Issued Types" in Workflow Scheme
Asked by Anette Noll:

Hi,  

I don't when and how I changed this, but this is not the default workflow.  
How can I change to another workflow?  

Thank you for feedback.  

<br />

<br />

![Jira_A.JPG](/t5/image/serverpage/image-id/339165i1970D68088DC79FD/image-size/large?v=v2&px=999 "Jira_A.JPG")


Answers:
author: Hans Polder
body: [@Anette Noll](/t5/user/viewprofilepage/user-id/4198653) ,

You can use the 'Add workflow' button on the top left to find the correct workflow, then assign it to 'Unassigned Issue Types' to update it :)

Be careful though, as it seems to affect 200+ projects according to your screenshot.

![Screenshot 2024-07-31 173118.png](https://community.atlassian.com/t5/image/serverpage/image-id/339177iCC4E5B171FD06D6A/image-size/large?v=v2&px=999 "Screenshot 2024-07-31 173118.png")

comments: author: Anette Noll
body: Hi [@Hans Polder](/t5/user/viewprofilepage/user-id/5506451) ,

thank you for response and support.

Everything "repaired" again.


Tags: cloud

jira-cloud
"The item is assigned to an invalid sprint."
Asked by mikkel lund:

Hi

I'm getting this error on some of the issues that are included in our portfolio plan.

*"Item ignored. The item is assigned to an invalid sprint."*

I have one project with three board, one team per board, paralelle sprints is diabled . (Is this not recommend?) All board are included into portfolio. Some of the issue have this error message. Did I do something wrong?  


Answers:
author: Dave
body: Hi Mikkel,

It looks like you might be experiencing the same issue described in this threads:

* <https://community.atlassian.com/t5/Jira-Core-questions/The-item-is-assigned-to-an-invalid-sprint/qaq-p/319548>
* <https://community.atlassian.com/t5/Portfolio-for-Jira-questions/Invalid-sprint/qaq-p/1852>

At the time of answering those questions we didn't have support for parallel sprints but we do now. I would definitely recommend enabling parallel sprints as this might resolve your issue.

I hope this helps,

Regards,

Dave


Tags: advanced-roadmaps

error

sprint

validation
How to consider the velocity of the past sprints in Portfolio
Asked by J?rgS:

Using Portfolio Cloud

I would like Portfolio to calculate the Issues in a sprint based on the velocity of the team.

Currently I can see the capacity and if the sprints are overbooked. I can also see in the Board in the Velocity Chart, that the team commitment is higher than the result.

I would like to see a realistic timeline where issues assigned to a sprint based on the capacity and velocity.

Is this supported by Portfolio?

Thanks,

Joerg


Answers:
author: J?rgS
body: Sort of. Try going into the Teams view and click on the number representing Velocity (pts) on the right side. In the popup that appears, click the Past Velocity tab and then click the *Use suggested velocity* button.

Not sure if it's exactly what you're looking for but it's the closest I can think of.

comments: author: J?rgS
body: Hi Steven,

yes, that is exactly what I'm looking for. Unfortunately there is no popup. I worked in a Server environment and I got this popup but in Cloud not. Is there a different functionality?


Tags: advanced-roadmaps

cloud
Picky customers and the case of the issue in two releases
Asked by Juan Carlos Gil Montoro:

Let me tell you my use case.  
We have a software base being enhanced and fixed by several teams, each with its own JIRA project and backlog. The software is used by a series of customers that may 'cherry-pick' what bugs/enhancements (issues) they are interested in for their own releases. This is intrinsic to the nature of the software and can't be avoided.  
So assume we have two teams, Team 1 and Team 2, each with three issues in their respective backlogs (1 to 3 for Team 1 and 4 to 6 for Team B). Now assume we have two customers, A and B, and let's say customer A is interested in issues 1, 3, 5 and 6 while customer B is dying for issues 1, 2, 4 and 5. Notice how both customers want issues 1 and 5, while other issues are requested by one customer only.  
(Please see the attached image for a sketch of this example)

![Portfolio case_large.png](/t5/image/serverpage/image-id/2124iE1B14823D4278646/image-size/large?v=v2&px=999 "Portfolio case_large.png")  
How could we configure Portfolio so that there is a "Release for customer A" including issues 1, 3, 5 and 6 and another "Release for customer B" spanning issues 1, 2, 4 and 5, provided we can't assign an issue to two different releases?  
Ideas welcome! \^_\^


Answers:
author: Juan Carlos Gil Montoro
body: I found the answer myself: the sentence "provided we can't assign an issue to two different releases" is actually FALSE, Portfolio and JIRA allows to do that.

So so far so good.


Tags: advanced-roadmaps
Fill parent link field by api or script
Asked by Thomas Hoffmann:

We build up a issue type hiearchy with linking three types by our own. The three types are Project - Change Requests - Task. We are using two link types. Now we decide to use portfolio. But we don't want to change our current kind of how we build our hierachy.  

We evalutate options how to 'syncronize' portfolio (using parent link) and our kind of relationship functionality.

For instance, we create a new issue and link that to an existing one. This hierachy (by linking) will not recognized by portfolio, so we need to fill in the parent link field (from portfolio) too.

Is it possible to fill in the parent link field without being at portfolio view and (re)do it manually?  

Thanks in advance  

Thomas


Answers:
author: Tarun Sapra
body: Hello Thomas,

It's a custom field, you can add it on the "edit screen" of the issue and manually enter the issue key from drop-down that appears.

This, should also be doable using REST APIs as it's a custom field and if you note down the cusotm field id then you can update it via REST API.

<https://confluence.atlassian.com/jiraportfoliocloud/showing-portfolio-custom-fields-in-jira-software-856708725.html>

[https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-edit-issues](https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-edit-issues?)

comments: author: Thomas Hoffmann
body: Thank you very much, but we found out that this field have a custom format which prevents from updating via mentioned ways.


Tags: advanced-roadmaps