John Funk Community Champion

Take a look at this previous post and see if that helps you. You are probably going to have to use the Advanced process. https://community.atlassian.com/t5/Jira-Software-questions/In-Jira-Automation-how-do-I-add-to-a-component-and-not-clear-the/qaq-p/2194124

What is the Customer Access you are using for the project? Go to Project Settings > Customer Permissions > Change the customer access settings

So, did that solve your problem?

Hi @FESSARD Simon Can you post a copy of the error you are receiving from the Audit Log? 

Did you try both suggestions of taking out "standardIssueTypes(), subTaskIssueTypes()"?

Hi Ash, This is a rather large question. It is probably better to post what specific type of metric is needed and whether Jira can accomplish that. And if so how.

Yes, if you delete the status from the workflow it will make you migrate all issues in that status that use that workflow - regardless of the project or board that uses the workflow. No, if you simply remove the status from the board column it will not cause the migration to happen. And issues can still be moved into and…

Welcome Nidal!

How is the Resolution field getting set? Through post function in the workflow? Through an automation rule? When you look at the history of the first issue type, who does he say updated the Resolution field?

Hi @011_avinash When you remove the status and save the issue, there will be a migration screen that appears where you will need to move any issues currently in that status to another status. 

Hi @Дарья Самофалова - Welcome to the Atlassian Community! Can you share some screenshots of the error? And some details of how you created the board? 

Sorry mate, but I am not a user of EazyBI. One of the other answers would serve you better. 

Is there something about the Epic that is known as it relates to the other issues? Is there a field populated with a particular value for example? 

Great! Glad it is working. 

Hi Sudhalakshmi - Welcome to the Atlassian Community! Can you be more specific as to your actual question? 

You need to check the Custom Fields to see if there is a Context associated with them that limit their availability to just the Task issue type (or at least do not include the Plan issue type). 

Hi LS, I have not experienced that. Can you share some screen shots/examples? 

Can you share a screenshot of the transition details from the workflow? 

Hi Arun, Can you provide some more clarity? You cannot move an issue type from one to another. You can move issues from one issue type to another. Or you can rename an issue type from one name to another. Which did you do? 

Hey @Finch Grace - Thanks for the information. Personally, I love the features. But PLEASE pass along to your fellow Atlassian product managers that ALL new features that get implemented out of the blue like this need the ability to be disabled - preferably at the project level, but at least at the system level. 

Hi @Мельник Ірина - Welcome to the Atlassian Community! You will want to vote for this feature request and follow it. https://jira.atlassian.com/browse/JRACLOUD-1991

Most weekends involve spending some time with our church family. Friday night Bible study, Saturday morning men's group and then worship on Sunday mornings. Sunday afternoons we usually have lunch in a nearby mall food court so we can spend time meeting new people don't know and having conversations with people from around…

Hi Adithya, You can only have one issue type scheme for a project. Workflows are associated with with issue types. So you can only have one workflow per issue type per project. However, you can have multiple issue types that use the same workflow. Boards, then, are associated with workflows - the statuses of workflows show…

Hi Ash - Welcome to the Atlassian Community! That's a pretty open ended type of question with lots of different answers. The real question is, what are you wanting to report on? And what metrics are you wanting to see? 

Hi Kalyan, Take a look at Revyz in the Atlassian Marketplace. Not sure if others can do that or not. 

You need to add the new employee with a new userid like normal. Then you can use the bulk change function to reassign all of the issues from the employee who left to the new employee. 

Hi Bhavik, You should be able to do this with Automation for Jira or ScriptRunner if you have one of them. For Automation, create a rule based on either an Issue Transitioned trigger (issue transitioned to Sent status) or a Field Value Changed trigger for the dropdown field. Then you capture the date in the custom field. 

Hi Jordan, I am afraid those values have probably been removed. Take a look at the history for one of the issues to see if it is in there. 

Hi @Hernan Funes - Did you end up taking another test? If so, which one?

Yes, you can set the {{issue.description}} only and it will overwrite the other.