John Funk Community Champion

Why don't you just assign the card to the user as a Post Function on the transition? Technically, assigning a user, even if it is themselves, is an "edit" of the issue. So you can't take that away from them. Then their rule (as we have in our organization) is NEVER assign a card to someone else. Only work on the cards you…

Hey Reynalda, The scheme is attached to the project and can be made up of multiple Field Configurations. Each Field Configuration can be attached to one or more Issue Types. The result is that you can make certain fields Required for certain issue types on a project but not others. 

Hi Reynalda - Welcome to the Atlassian Community! You need to create a new Field Configuration (and Field Configuration Scheme) for your project. You can get guidance for doing that here: https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

Someone with ScriptRunner would have to answer that. Send them a support request and see what you get from them. :-)

Jira does some things based on the type of project and board where it is expecting Done to be the last column on your board. So my first question is why aren't you just letting Done be the last column? If it is Done why do you have to Close it later? The trick comes into when you are setting the Resolution and there is…

You should be able to do that with the board filter itself, just take into account the status. Something like (Project = ABC and status = Backlog) OR (Project = ABC and issuetype = Sub-task)

Hi Hemant, Let me see if I understand. The analyst project role no long has Edit issue permissions. But the analyst project role has permissions for Transition issue? But the analyst is not able to transition an issue. Is that correct?

The way to solve that is to first copy the workflow, then make your changes to the inactive workflow. Then update your Workflow scheme to sub out the old workflow for the new workflow. Just make sure you match up the appropriate Issue Types when you add the new workflow. The publish the modified workflow scheme. 

Here is the link to submit a request: https://support.atlassian.com/contact/#/ But maybe we can help you here. Are you able to access the Workflow? But just a note, you cannot modify workflows for Next-gen projects. 

Ah, alors laissez-moi voir si je peux créer un ticket pour ma propre instance et ensuite vous le faire savoir. :-)

Hi Christa, Have you verified that the new Acceptance Criteria issue type is available for the project you are using? In other words, have you added it to the Issue Type Scheme used by the project? 

Hi Darryl, I doubt Automation For Jira is going to be able to do what you have in there, but will let Support provide you with the expert response. Have you thought about filtering out those emails using JQL and then creating your Email rule just against the appropriate filter(s). You might need to create multiple rules to…

Hi Amy Jo, Try this in the field in Automation For Jira: {{issue.description}} Type next text here. That should keep the existing text and then append your additional text. You can actually put the existing text field at the bottom or in between if you like. :-)

Hi Yvette - Welcome to the Atlassian Community! How are your Tasks connected to your Story? There is no built in relationship with Jira between those two issue types. Second, just realize that Next-gen projects are extremely easy to use and get started with. However, they provide very little functionality to customize.…

Hi and Welcome Pedro! We are glad you are here!!

Hi and Welcome Courtney! We are glad you are here!

Hi Patrick - Welcome to the Atlassian Community! There's at least two different ways to approach this, maybe more. But I will offer two. :-) 1. Change the filter used by the board to only show what you want. Now, IMHO, I think that might be overkill for what you want. But up to you. 2. Simply create a Quick Filter on the…

Hi Paul - Welcome to the Atlassian Community! Here's my limited understanding of how all of this ranking stuff works. I can't even verify that I am correct in my assumptions because it makes my head hurt to think about it as well. My theory is that when you use the ORDER BY Rank for the board filter that it somehow ranks…

Hi Pavel - Welcome to the Atlassian Community! You should be able to create a simple Automation For Jira rule to do that. See this for more information. If you need additional help, just post back here. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month *…

Hi Ron, Navigate to Settings > Issues > Workflows Then edit the appropriate Workflow to see the transitions and conditions. If you are not sure which workflow is being used by the project, then navigate to Project Settings > Workflows

Hi @Marcília Nascimento - Welcome to the Atlassian Community! I am sorry, but you cannot restore the left side navigation. Atlassian has moved everyone to the top navigation only as a permanent change. 

Je suis vraiment désolé, mais je ne trouve tout simplement pas le nom du champ. Je vous suggère de créer un ticket d'assistance pour Atlassian pour voir s'ils peuvent vous aider. Ensuite, veuillez poster ici avec leur solution. https://support.atlassian.com/contact/#/

Make sure that Project Role (atlassian-addons-project-access) has Create issue permissions. 

Are you sure all of the permissions are there? Take a look at the Create Issue permission in the permission scheme for VCANDROID and compare it to the permission scheme for MI.

Hi Iryna, Can you post a screenshot of the error you see in the Audit Log for the rule? 

Since you are changing issue types and they have different workflows, I do not think you will be able to do that would automation. 

Você só pode criar um único campo com dois níveis de cascata no Jira Cloud. A primeira parte do campo pode ter valores de A, B, C. Então, se o usuário selecionasse A, a segunda parte do campo poderá ter 1, 2, 5, 6. Se eles selecionassem B, obteriam 1, 2, 4, 9. E assim por diante.

It also looks like they have done all that they are going to do with this. Basically, they are giving a message that you might want to refresh as something was updated. But they don't want to implement an auto-refresh as it might drop other editing the user has started. 

Hi @sreuter - I tried the above documentation but it is a little misleading. The trigger returned nothing if I used issue. and the name. (Also the documentation has an (INSERT SCREENSHOT HERE) prompt but no screen. ;-) So what ended up working for me was this: {{#lookupIssues}} * <a href="{{url}}">{{key}} </a> |…

Well, that's not very nice of it to do that to you. ;-) I tested the below and got good results dropping the issue. in front. The documentation does not include priority, so I dropped that out to. I will ask them about that. {{#lookupIssues}} * <a href="{{url}}">{{key}} </a> | {{created.longDate}} | {{status.name}} {{/}}