John Funk Community Champion

Hi Paul, No, custom fields cannot be shared across Next-gen projects. You have to create the field on each project. 

Hi Emily - Welcome to the Atlassian Community! Check the Permission Scheme for the project to see who has Browse project permissions. 

Welcome Paul! We are glad you are here!!

Hi Nikhil - Welcome to the Atlassian Community! You might creating a Dashboard and add an Issue Statistics gadget to the Dashboard. Configure the gadget to use the Assignee field as the Statistic. (or whatever field has the Developer's name). This will group the list of issues by the Assignee. 

Ouch - my initial idea probably would not work then. So one idea is to create a transition from the Backlog status to a new status like Reviewed or Assigned or something like that in the workflow. Then attach a transition screen to the transition that just has the Assignee field. Then you create a board with just the…

Thanks for the insight. How many different people might be assigned a card?

So when the QA analyst updates a custom field to say PASS or SKIP (is it a field or a transition to a status?) if the UAT required field says Yes, then you want to auto transition the card to User Acceptance status. Otherwise it should auto transition to Ready to Release. Is that that scenario? If so, you can easily do…

Hi Marine - Welcome to the Atlassian Community! Correct, the only way out of the box to assign a card is to open to edit it. Do you have to do a lot of assigning of cards? In what circumstances are you assigning cards? Could any of that be automated?

Great, glad it worked! Have a great weekend, too!

Great! Glad I was able to help.

Ah! I had just assumed that was in the filter. Sorry for not asking about it. Glad you found the fix. 

It is if you are moving current issues to the new workflow and they are in statuses that don't exist in thew new workflow scheme. As it moves them, it will prompt you for the mapping. :-)

Hi @Thi Tran - Make sure you are a Jira Administrator and not just a Project Administrator. As a Jira Administrator you should be able to create Projects. Are you trying to create a Classic Software Project or a Next-gen Project?

Hi Buck, Congrats on the move to Kanban! If you simply move your existing project over to the new workflows, you will have to map the existing statuses that are not in the new workflow to a status that is. It's simply a part of the migration process when connecting a project to a new workflow scheme. The Backlog and Done…

Hi Raoul, You can create two transitions leaving the QA status - one to User Acceptance and one to Ready to Release. Then put a condition on each transition that checks the value of the UAT field. 

Hi Stephen - Welcome to the Atlassian Community! It sounds like there is a required field somewhere. Maybe take a look at the Create transition in the Epic workflow to see if there is a Validator attached to it. Or like at the Field Configuration to see which fields are Required. 

Hi Fiona, I would suggest you put in a Support Request with Atlassian. This might be a bug or new direction from them. But I think only they will know at this point. https://support.atlassian.com/contact/#/

Hi Bond, I have not tried to base Swimlanes on Epics before, but what I noticed is that the cards that are attached to Epics are the ones that have disappeared. It would be interesting to see what happens if you link the LUNA-189 card to an Epic. 

Hi Andreas - Welcome to the Atlassian Community! I would use Automation For Jira to send the notification. You can control the message, who you want to send it to and for which issue types. * Go to Project Settings > Project Automation (on left-hand menu) * Press Create Rule in top-right corner * Select the Trigger "Issue…

The issue type name is not visible in the new view. Only the icon.

Yes because only Agents can make changes to tickets.

Hi Eudora, You can place a validator on the transition in the workflow that goes to the status where you want to already have been filled in. Just create a Required field validator on that step. 

My point was that if you are requiring the user to select every box in the checklist, why not mark it for them automatically as a byproduct of the transition. Why make them check off every box when you can automate that step and speed the process? There there is no reason to validate it - it will always be selected. 

Great! :-)

Hi @Ureee , Validators just prevent a user from transitioning an issue based on the criteria. Then it gives a message as to what the problem is. I think what you would also like is a transition screen that would pop up with the Assignee field in the screen. You would need to create a screen and place just the Assignee in…

It might be easiest to just add a sub-filter to the board to not show them after a specific time. 

Let me know if it works. :-) You might want to look to see if there is some type of automation already that is setting the assignee = reporter because it does not automatically assign me to issues I create in our Next-gen projects. 

Great! Glad you have a solution!

Hi Andrei, You could set up an automation for Jira rule to clear the assignee after it gets created.

That's very weird. I would submit a support ticket to Atlassian. https://support.atlassian.com/contact/#/