John Funk Community Champion

Hmm - are you trying to Delete the issue directly in the Issue View? Or from an outside source?

Hi Pavel, You also still need the correct permissions in the Permission Scheme. Make sure you have Browse Project permissions for that project. 

Hi David - Welcome to the Atlassian Community! Issues (tasks/cards/stories, etc.) are not created on boards per se, they are created on a Project. Then the board using a filter connected to a project to tell the board which cards/tasks, etc. should show up there. So, you can have a card that shows up on two different…

Hi Perry - Welcome to the Atlassian Community! Have you check the Permissions Scheme attached to the project to be sure you have permissions to Delete Issue?

Hey Thom, I would go ahead and create a support ticket with Atlassian for that. I don't know of a reason why it would fail like that and not for other fields. The only difference being that Request Participants is a multi select field and the others are single select. https://support.atlassian.com/contact/#/ You might also…

Great! Glad it is at least mostly working for you. :-)

You have to be a project admin to be able to modify the simplified workflow. Or if you are a Jira Admin, then you can go to Settings > Issues > Workflows and modify it there. 

Great - please do!

Yes, sorry about the syntax error. 

Great - glad I could help out. Good Luck!

Hi Nelson - Welcome to the Atlassian Community! I would encourage to use a third party add-on like Nave or Actionable Agile. 

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

Ah, that's helpful. :-) You should be able to de-activate a user at any point. Just go to Settings > User Management. You have to have site-admin privileges to be able to do that. 

Yes, I stumbled onto it myself many weeks ago. :-) I am glad it is working for you now!

Hi Marwa - Welcome to the Atlassian Community! Are you using Jira Service Desk for either project? What if you created a single workflow that went through all of the steps you described. Then moved all of the issues from Project B to Project A and closed out Project B. Connect the new workflow to Project A and route the…

WOW. I would open up a support ticket to ask Atlassian about it: https://support.atlassian.com/contact/#/

Instead of using the Assign Issue action, maybe try using Edit Issue instead. Then select Assignee field. Then click the 3 dots and select Copy from Current Issue. Then click on the words Current Issue which will popup the ability to select another field to copy into the Assignee. 

Sure that makes sense and should be easily doable with Automation For Jira. And it comes free with Jira Cloud now. Here's some information to get you started. Feel free to post more questions for additional help. :-) There are two types of automation: * Global: In the Free version, you get 100 executions per product, per…

Hi Marek - Welcome to the Atlassian Community! I would encourage to watch this webinar on Automation for Jira from last week. Towards the end there is a use case where Jira can use Automation to start a build process in Jenkins. It should be fairly similar to what you want to do with ITSM (BMC).…

Sure, start with this and see if it helps guide you. There are lots of resources and webinars to help you learn more about it. It is a very powerful and easy tool. 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…

Great! Glad I could help a little. 

Hi Adam - Welcome to the Atlassian Community! I am not sure how you would do that other than if you check for every other value that might be in Issue 1. If there are a lot of label possibilities, you are probably out of luck. At least for my knowledge. 

I would go ahead and open a support ticket with Atlassian then for the Automation For Jira folks. https://support.atlassian.com/contact/#/

So the Verification Automated? field only exists in the linked Test tickets and not the parent/trigger issue?

You have to add a new transition that loops itself from Done to Done. Then you put a post function on the new transition to set the Resolution to Done. Then you can do a bulk change and transition all of the issues with the new looping transition. 

Great! Glad it is working for you. Can you click on the Accept Answer button above to close this one out? Thanks!

Glad I could help!

statusCategory actually picks those up already. Status fall into one of 3 categories, Done, To Do, In Progress. So if the statusCategory = Done it should get the Rejected ones as well. Did you run the query to see if anything is missing?

I would just prevent them from moving to Done from To Do. Make them at least pull through In Progress. So other than that, the rule is now working for you? 

Great! Glad it is working for you!