John Funk Community Champion

Hmm, since you are running it through Crowd, you should probably open a support ticket with them. 

Hi @Jyothi Ravipati I am a little confused by your question. Why can't you just add the validator to make the field required? It shouldn't have anything to do with your automation rule that fires on create, unless your validator is on the Create transition. 

Thanks for the opportunity!

Hi Sonia, I would open a support ticket with Atlassian to see if the email address might have been blacklisted. https://support.atlassian.com/contact/#/

Hi Colleen - You can create a Team and place all of the users in the Team. Then you can @ the Team name.

Hi Bill - Welcome to the Atlassian Community! The approver configuration is only available for Workflows connected to Jira Service Management projects. Also, the Workflow must be active (connected to a project) to be able to configure the approval. 

Hi Ricardo, You probably need to do a Bulk Change for those issues where the Reporter is no longer an active Jira user. But there must be a value in the field, you can't just clear it. So you will need to replace with an active user. 

Hi @[deleted] Here is the rule we use:

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

Great! Glad it was helpful.

You are welcome!

Hi Ravipati, You will need to contact Atlassian Support here: https://support.atlassian.com/contact/#/

Hi Anna - Welcome to the Atlassian Community! Yes, they can coexist. :-)

Hello and Welcome, @Mai Huong Nguyen We are glad you are here!!

Hi Douglas, You can see the execution limits in this article. Scroll down to the Automation part. https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Hi Zoe - I wouldn't create a scrum board if you are not really running scrum and sprints for the work. Just create a board with a filter that includes the issues you want to see. Then you can simply click on the avatar of the assignee to see that person's tickets. 

Hi @Jamie Davies - I got some feedback. If you go the workflow used by the board and do an Edit of the workflow and then Publish it, it should all be good again. I know you might not have a draft workflow already going, but this works. And, yes, I know you shouldn't have to do that, but until they get a fix, that's the…

Hi Werner - check to see if there are any Conditions on the transition from Open to any of the other statuses. 

Welcome, welcome, Linda! Thanks for putting in a good word for us in New to JSM. :-) Also, let us know how it goes for you as you begin using JWM. 

Hi @Md Zubeda - Welcome to the Atlassian Community! You could do this by applying issue level security when the issue moves to a particular status. You would use an automation rule that uses an Issue transitioned trigger for the transition to the related status. Then do a new Action and update the Security Level field. You…

Hi James - Welcome to the Atlassian Community! This sounds like mostly an education issue. Also, why are you having non-software teams do Scrum? They are probably more suited for Kanban or something fairly simple. Can you describe the workflow the non-software teams use - as in what types of statuses? 

Yes, if you create a separate quick filter for each issue type, it will eventually become a dropdown anyway. 

Sure - here is some more information if you are not familiar with automation: 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:…

I am not a programmer either and don't use those tools - just know that's the probable solution. 

You shouldn't have a separate password from Jira apart from Atlassian. It should just be your Atlassian password. 

Hi Caroline - Welcome to the Atlassian Community! Are you getting other emails from within your Jira? Like with mentions in Comments or other email notifications?

Hi Samuel, In your first screenshot, just click on the General Bug Screen link there. Then you can add/remove fields and change the order. 

Hey Elena, You might find this previous post helpful: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-may-I-increment-a-custom-field-s-number-on-a-specific/qaq-p/742636

Hi Gerhard, You should be able to do this to create the custom field: * Go to Settings > Issues > Custom Fields * Click Create custom field * Click on Advanced on the left hand side * Click on Insight objects * Give it a Name * Click Create button Then you should be able to configure it to map it to one or more Insight…

Sounds like someone has the voodoo doll out on you