John Funk Community Champion

Hi Michal, It's probably a timing issue with Automation. Maybe try inserting a Branch before the Edit Issue action for Most Recently Created Issue. Then stick the Edit Issue under that. If those fields are still not getting there, try adding a Log statement to see if it is seeing the fields from the parent. Then maybe add…

So, what is different about the two tickets - the one you can see and the one you cannot see? You need to look at every single field to see the difference - including Issue Type, Request Type, etc.

Once again, the users will not see the Raise this request on behalf of field. 

Hi Rodrigo, Automation cannot force the user to enter a value. The rule itself can enter a value (i.e. update it) but can't force validation. 

Hi Rodrigo - Welcome to the Atlassian Community! It's a little hidden, but just drag the rule name over to the Category on the left and drop it. 

Hi Luis - Welcome to the Atlassian Community! Yes, create a Scheduled trigger run to run once a day. Add a JQL query to the trigger to get the issues. Is there a particular field that needs to have a value? Then add an action for Send Email.

A JSM Agent is a user who has been granted that permission to the Jira Service Management product. They should also be in the Service Desk Team role in the project. 

Which field do you want to remove?

Sure - you can create custom fields - you can do a short text field and call it Your Email Address or whatever. 

Super admin still has to abide by the Permission scheme associated with the project. There really is not "super" admin who can do anything he wants at anytime. 

Please keep your responses in this thread so that readers can follow the conversation. You need to remove any project that is already connected to an existing Context before creating others. 

Yes, if the user is not a JSM Agent, they cannot see the issue outside of the portal view. So they can't click on a URL and go straight there. 

Hi Rahul - Welcome to the Atlassian Community! You can't trade userid's for users. You can deactivate the one that left and then add the new user so it doesn't take up an extra license. What exactly are you trying to accomplish? 

Hi Kyana, The Request Type field is not available for JWM projects - just JSM. You would need to setup the normal email handler function to create issues from Emails if that is what you are looking for. 

Hi Hayden, You might check out Atlassian's answer in this post: https://community.atlassian.com/t5/Team-managed-projects-questions/How-to-disable-quick-edits-on-board/qaq-p/2406222

こんにち - @[deleted] アトラシアン コミュニティへようこそ。 上書きを防ぐには、デフォルトのテキストの前または後の「説明」フィールドでこのコードを使用します。 {{問題の説明}} また、それが正しいかどうかを確認するために、ルールを共有してもらえますか?

Hi Tina - Welcome to the Atlassian Community! You can't really download a list of projects out of the box. You might be able to do it with an API call. What I usually do is Copy on my monitor and then paste the list into Excel and then do some clean up. 

Team-managed projects by default only show the Done issues for two weeks on the board and then they disappear. If you need something more powerful/flexible, you can create a second board. Here is some guidance on how to do that is you want. If the article is helpful, please give it a Like. :-)…

Hi Lawrence - Welcome to the Atlassian Community! I think Atlassian views it as the requester should not be assigning the work, but someone else in the team performing the work. Therefore the Assignee field is not supported. I don't see that changing anytime soon. So a work around is to include another field with maybe a…

It should just default to Global for the new ones. You can scroll all of the way down on the right to see if any projects are selected. You can't have multiple contexts with different projects - all of them have to be global. 

Hi Muhammad - Welcome to the Atlassian Community! No, not with a Team-managed project. You can do it with company-managed projects using the issue level security. But that is not available for Team-managed projects yet. 

All of the Community Managers and other Atlassian employees that support us, encourage us, put up with our (my!) foolishness, and attend to our every need. Y'all are the best!

Would you be so kind to click the Accept Answer button above so we can close this one out? Thanks!

Great! Glad that worked for you.

I would go ahead and open a support ticket with Atlassian.

Maybe because some users do not have the permission to create issues on the new project?

Duplicate 

Check the Notifications Scheme for the project to see if the Administrator role is receiving stuff. Is that the only Role you have on the project? Are you also a Jira Administrator? Or just a project Administrator? 

Then you should be able to create a different Context for each issue type. Leave the projects as Global. 

Hi Sebastian, Conditions for workflows are very different than automations. Conditions allow (or prevent) users from executing transitions. Automation rules fire as a result of an action that happens (like the issue was transitioned). What exactly are you trying to do?