John Funk Community Champion

Are you not a Jira Administrator? Can you update the values of Custom Fields? That would be where you add the Assembly Numbers. But it needs to be created as a Select List (single choice) type of custom field. Then you can add the values. You should be able to take a screenshot of the board if you like. Just hide any…

Just got notified of the link to the bug and some workarounds: https://jira.atlassian.com/browse/JRACLOUD-75040 I suggest to vote for and follow it. 

Make sure each user has Jira Software or Jira Core access in the Settings > User Management area. You will need to be a Jira Site Administrator to get there. Also make sure they are in the jira-users group at the very least. 

Hi Bobbi Jo, Yes, you can create a different Field Configuration for each issue type. Then all of the Field Configurations are grouped together in a Field Configuration Scheme and the scheme is attached to the project. Each Field Configuration can have different required fields. Likewise, you can have different screens…

Hi Noren, Changing the status of the Issue will cause it to move from the Backlog to the Board no matter what frontend you are using. Are you able to change the status of the Issue in the mobile app? 

Hi Osman - Welcome to the Atlassian Community! Make sure that the user has Jira Software (or Jira Core) permissions at the user level. Then make sure that the user has Browse Project permissions in the Permission Scheme for the project. 

Hi Dave, I guess the first thing to recognize is that you don't really create cards/issues against a board, but against a project. So regardless of what board you are on when you click the Create button, you need to pay special attention to what Project it is defaulting to and change that if need be.

Maybe there is a post function that is setting the value. I would check the workflow for the Create transition to see what is going on there. 

Hi Judy, Because there is a bug in Jira right now that when a ticket with a resolution gets cloned, it also clones the Resolution value. Not sure when the fix will come. In the meantime, I have created a post function to clear the Resolution field on the Backlog status (self looping). 

Jira has a bug right now that they are working so it won't keep happening. But not sure of when there will be a fix. So you might have to periodically run the transition. 

Hi Fernando - Welcome to the Atlassian Community! To delete an issue (including Epics) you must have permission to do so in the Permission Scheme attached to the project. 

Hi Alissa, Create a looping transition on the Done on the Backlog status (or whichever status has the issue in it). Then put a post function on that transition to Clear the Resolution field. You might want to also add a post function to Clear the Resolved field if it has a value in it (it's a date field). 

Hi Jaspreet, I don't know why Atlassian creates both of those with the same name as a default, but I would change one of them. That's what we did and is works fine now. Go to Settings > Issues > Issue Linking to make the change. 

Hi Theya - Welcome to the Atlassian Community! It's hard to tell what you are encountering. Can you give us a step by step what you are doing and what it is showing?

Hi Vishal - Welcome to the Atlassian Community! Simply put, you will not be able to do that without an add-on. 

I also use Cloud. :-) Start by reviewing here: There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited executions per month Automation Basics: https://www.atlassian.com/software/jira/guides/expand-jira/automation You can…

Hey Ian, You could probably update the parent with the value of the Sub-task as each Sub-task is created. And probably even as the component field is updated for each Sub-task. But I don't know about doing that on existing records where the values are not being updated. 

Hi Christine, What we have noticed it that when we clone an issue it is copying over the Resolution value even though it is placing the issue in the Backlog. I have a bug opened with Atlassian to try to get that solved. The Resolution should be empty in the newly cloned issue. 

Hi Meletis, I don't know what is causing your problem, but there might be a workaround. What statuses have changed between the workflows? 

Thanks, Stephen. What's the ramifications of that? I am not currently using Atlassian Access but hope to real soon. What impact would that have on Access? 

Can you try it in an advanced search? Type in resolution = and see if it comes up in the list there or if you type it in. 

Hi Benjamin, Maybe you could add an If / Else block to check the status after the trigger fires? If In Progress, then transition the ticket, else send the email. 

Hi Craig, You should be able to make it a multi-project rule and list all of the projects it should run against. 1. Go to Rule details 2. Change the Scope to Multiple projects 3. Add the projects

Hey Curt, Can you share a screenshot of your rule?

Yes the reporter is the creator of the ticket. But it is strange that your mail handler would say that Jira Automation is the creator of the ticket, unless you are using Automation for the actual handling of the the creation. Is that case? How is your mail handler functioning? What does it look like?

As Florian said, you can do that with the Bulk change functionality mentioned above. But since you are using Jira Cloud, you do not have access to the database to make changes. So the Bulk change is the best way to go. 

Well, that's very weird that Jira Automation would be the Reporter on the mail handler. Is your mail handler setup that way? Your other option is to set the value with a post function on the Create transition in your workflow. If there are other conditions involved with that which you can't handle in the post function…

Hi Jelle - Welcome to the Atlassian Community! There are a couple of ways to approach it. The best would be to modify the workflow for that project to create a transition between the Abandoned status and the Backlog status. Publish the workflow and then you can make the transition. If you cannot modify the workflow for…

Привет, Екатерина! Добро пожаловать в сообщество Atlassian! Вероятно, вы сможете делать то, что хотите, с Automation For Jira. Вот некоторая информация для начала: Есть два типа автоматизации: * Глобальный: в бесплатной версии вы получаете 100 выполнений каждого продукта в месяц. * Проект: во всех версиях вы получаете…

Hi and Welcome, Melany! We are glad you are here!!