John Funk Community Champion

So is this now working for you? 

Yes, it is probably because it is a Next-gen project. Try using this code: { "fields": { "assignee": {{issue.Developer. accountId}} ] } }

Hi Artur, I will see if I can get someone with Atlassian to help you out. 

Hi Chris, Can you share some screenshots of the issue layout screen that is being used, that shows the Description field? 

Hi @Anuradha Yadav - if the project uses the Simplified Workflow created with the project, then a Project Administrator should be able to modify the workflow. If the workflow is shared with other projects, then it can only be edited by a Jira Administrator.…

Hi Nishant, You cannot limit access to fields in Jira cloud by standard means. The only way I have found to be close is to remove the fields from Edit screen as a whole. Then create a Transition screen with the fields that you want to allow update to for some people. Then add the transition screen to a new looping…

Basically, yes. But to keep it from showing up in the list of boards for that project that it might not apply to, it is better to create a generic Classic Software project for this purpose as Jack suggests. 

Hi Nick - Welcome to the Atlassian Community! I am a little confused as to whether you are on Cloud or Server. Your message says Server but this post has Cloud as the Deployment Type. If it is indeed server, then Next-gen projects are not available for Server. See this request to have that…

I have created a Classic software project for Basic Next-gen Project links like that. You can link it to any project that you can which will allow you to get to the board from within that project. But you will still only see cards from the filter you attach to the board. 

Hi @Nouha Ben Abdallah - Welcome to the Atlassian Community! You should be able to create the board and attach it to a filter for the Next-gen project you want to use. You might not be able to attach it to the Location for the project though. But that will not keep it from working against your project. 

Hi Alicia, Yes, the history will move with it. However, it is always good to do a single test card first to verify. :-)

Hey Frank - Are you a Jira Administrator for the instance? Maybe go to all projects and see who the project lead is for each project.

Hi @Viktoria Lukinova - Welcome to the Atlassian Community! I don't think you can do it by column, but you could probably do it by Swimlane. 

Can you provide some screenshots and step by step what you are doing?

Hi Rick - Welcome to the Atlassian Community! I am not sure what you are want to show, but gadgets on a dashboard are usually as simple as basing them on a filter. And you can create a filter that shows multiple projects. Something like Project in (ABC, DEF, 123) Is that what you are talking about? 

Hi Maria - Welcome to the Atlassian Community! I am experiencing the same thing. It's probably best just to ask Support. https://support.atlassian.com/contact/#/

And can you post the audit log for this new rule for when you run it? I assume it still does not send the email?

Hi @Retail Italia Amministratore - Welcome to the Atlassian Community! If I understand you correctly, you are expecting the rule to copy the priority from the Epic to a a Task when you create the task from the Epic. However, this rule only fires when the Priority changes, not when a new issue is created. You should change…

Go to Settings > User Management and search for the user. You will need to have Site Admin permissions to do that. 

Debería ver algo como esto: ¿No ves eso? Si no es así, ¿puedes compartir lo que ves?

Just the person? Are others showing up? Can you see the Add people button? It should look like this: Do you not see that? If not, can you share what you see? 

Is the person not showing up when you click on the Add People button?

try just tying the username without the autocomplete. For example, john.funk

Hola, Leidy. ¡Bienvenido a la comunidad de Atlassian! Vaya a Configuración del proyecto y luego seleccione Personas. Luego haga clic en Agregar personas. Allí podrá vincular a una persona a un rol en el proyecto.

Hi Paula, Make sure the user is included in the Assignable User permission in the Permission Scheme for that Project. If might also be that it won't allow it if the user has NEVER logged in yet. But I have never run into that scenario. 

Ah, that helps me to understand. I don't think you are going to be able to put the actual name of the field in the email like that. Just the values. I was suggesting a different Rule for each field changed. For example, modify the rule to just fire when the Report Type changes. Then in the email body, put Report Type: in…

Hello and Welcome, Brent! We are glad you are here!!

Hi Jack, I think you need to put a label for the field in the actual email. It will look a little wonky but will be descriptive. Or you could copy and past the email component and use a separate email component for each field. 

Lo siento, aqui: https://support.atlassian.com/contact/#/

Hi @somnath.yadav - try creating a filter like: status changed from "In Progress" to Backlog Just adjust the names of the statuses for the direction and status names that you want.