Comments
-
No, no estoy hablando del correo electrónico que recibe, sino del componente Enviar correo electrónico en la herramienta de Automatización. Mira mi captura de pantalla. ¿Puedes compartir lo que tienes?
-
Hi Mamikon - Welcome to the Atlassian Community! You should be able to click on the little bell icon near your avatar to see notifications in the browser.
-
Hi Madeleine - Welcome to the Atlassian Community! You can't sort columns separately on a board. You can only have one sorting for the entire board. And even that is not usually a good idea because as soon you add the sort to your filter, you lose the ability to drag cards up and down in the column to prioritize (rank)…
-
See this article on permissions for JSD: https://community.atlassian.com/t5/Jira-Service-Desk-articles/Tips-for-setting-customer-permissions-in-Jira-Service-Desk/ba-p/1340617 If the "customers" are not Jira users, then they will not be able to raise the request. In other words they would not see the field. I would create…
-
Unfortunately, I don't. But you might find it will go quicker than you thought once you get the initial filter written. :-)
-
Hi Chandan, You can see more in the following post: https://community.atlassian.com/t5/Jira-questions/Convert-emails-to-Issues-and-Tickets/qaq-p/704512 But the short info is here: 1. You can read about mail setup for customers here https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html…
-
Great - glad I could help!
-
Glad I was able to help. 🙂
-
Hi @Chethan GR - most likely you are seeing that field because you are a Service Desk Agent for that project. Your customers will not see the field.
-
Hi Nofar - it’s a beautiful work but you can do it. You can do query combination for fields being populated. For Each query do a bulk change and select the items that were already selected and add your new one. For example do a query where the custom field = A and custom field != B and custom field != C and custom field !=…
-
Hi @[deleted] - Board r filter would look like this: Project = RSA and “custom field “ = “Transactional” ORDER BY Rank ASC Board s: Project = RSA and “custom field “ = “Statements” ORDER BY Rank ASC
-
Hi Dellie - Go to Settings > Issues > Workflows. You must be a Jira Administrator to see them.
-
Hi Victor - Welcome to the Atlassian Community! click on your avatar, then select Personal Settings. About halfway down the page under the section for Jira Labs turn on the New Jira Issue View
-
Great - glad you got it to work! If this took care of the problem can you click on the Accept answer button above to close this one out? Thanks!
-
Did that work for you, Alex?
-
Hi Ryan, The transitions still have to exist in the workflow. But instead of putting post functions on those transitions, you can implement that functionality with Automation For Jira.
-
You can attach it to only one Issue type. So, you would have a Field Configuration Scheme with multiple Field Configurations - one for Sub-task and one for everything else.
-
Hi Alex, Just create a new board where the filter is something like: Project = ABC and issuetype = Epic ORDER BY Rank ASC Then only map the Backlog status to a single column on your board. Would that solve what you need?
-
Right after the create of the sub-task, put in a component for Branch rule / related issues. Then choose Sub-tasks or Most recently created issue Then add a component for Edit issue to update the Assignee field. Copy it from the parent.
-
Awesome - thanks, @Daniel Eads !! Is there any way to be a Watcher on that to get updates automatically?
-
Great! Glad I could help.
-
Hi Brian - Welcome to the Atlassian Community! I will see if I can get an Atlassian team member to help you out.
-
Hey Tim - Finally ran across this: https://jira.atlassian.com/browse/JRACLOUD-71712 So you should vote for that and follow. But bottom line for now is that it can't be done. You have to create multiple fields as you have done which leads to all of the other problems. But I know that there are certain functions in Jira that…
-
Hi @Евгений Фарсалов - You can modify the Field Configuration for that project to make the Linked Issue field required. Then you would need to add a validator in your workflow to set the value of the Linked Issues field to the desired type.
-
Great! If that takes care of it for you, can you click on the Accept answer button above to close this one out? Thanks!
-
Hi Kate - Welcome to the Atlassian Community! Simply click on your avatar, then chose the option to Turn off new navigation.
-
So you want to run the filter like I have above, and then create a link between the two issues if one does not already exist?
-
You could capture the value in the Manager field and then copy it over to the Approver field. That's typically what I do.
-
Hi Saadoon, I don't think you are going to be able to get that in a single filter that can be exported. As you said, there is no link between Epic and Sub-task, so you HAVE to use the Sub-task parent at the middle man.