John Funk Community Champion

Hi Jeff - Welcome to the Atlassian Community! First, I would suggest you edit the question to remove your email and phone number - it is currently visible to the world. Next, what type of field is Criticality? And what do the values in the field look like?

Hi Pavel, Did you ever get any assistance for this from the Vendor? 

Can you share the entire rule as you have it built?

Hi Thomas - Welcome to the Atlassian Community! You mentioned that both projects were JWM projects. But are they both the same type? Are they both Team-managed or Company-managed projects? Or are they one of each? 

Ah, it sounds like you might be using a Team-managed project. Can you verify if it is Team-managed or Company-managed? Team=-managed projects do not use schemes. 

You are welcome. I would love to see your finished, working rule when you get to that point. Also, feel free to ask more questions along the way to help get you there. 

Hi @Dogan Cibiceli - Did you try Nic's suggestion? 

Hey Kevin, That sounds like it works for everyone involved - I would give it a whirl and see how it works out. 

@Alex Hoogendoorn You should be able to create an automation rule to do that for you. I would actually create a new custom field called Epic Summary or something like that - but not Summary which would cause confusion. The field should be a Short Text field. Then Create a Scheduled trigger to run once a day. Add the JQL…

Take a look at this previous post to see if it helps you get started: https://community.atlassian.com/t5/Automation-questions/Automate-quot-Target-Date-quot-field-when-ticket-is-moved-to/qaq-p/2251838 https://community.atlassian.com/t5/Jira-Software-questions/Output-of-linked-tasks-using-smart-values/qaq-p/1646118

Привет @Евгений Сальников - Добро пожаловать в сообщество Atlassian! Извините, но я не могу сказать, на каком это экране, так как не знаю русского языка. Можешь перевести псевдоним на английский? Кроме того, почему вы хотите скрыть значение?

こんにちは - アトラシアン コミュニティへようこそ! 詳細を教えていただけますか？ 作成時にフィールドのデフォルト値としてテーブルを含めますか?

Hi Javan - Welcome to the Atlassian Community! Unfortunately, there is no history function on the Flagged field. So getting Flagged = Impediment will only show you issues that are currently Flagged, not issues that were Flagged at anytime during the month, year, etc. So, you will probably need to create a custom field…

Hi Trevor, Can you share the rule where you are creating and linking the task? Have you tried to copy the comments from the parent task at the same time? 

Hi @Yong Yang It's probably still just a timing thing. The Re-fetch only takes a second or two, and the webhook is probably taking longer than that. You could try adding another Re-fetch or two after the initial one to see if that helps any. Another option would be to create another automation rule that doesn't fire until…

Yes, remove the Story Points field from the Create screen. And click the Add fields option beside the name of each Sub-task creation and make sure there are values for each required field for the Sub-task. Get the 7 done then we can deal with the 8th one. 

No, by workflow, I mean the statuses or steps in your workflow. Add a new status from Backlog called Template or something like that. Create the issue and getting it the way you want it and move it to the Template status (or whatever you call it. Then you can simply clone it when ready for a similar issue. 

Hi @Fabian Dengel - Please create a new question so that more people can see it and answers can be tailored for your exact need. 

Can you include the rule here? Also, make sure that the person you are copying to the Assignee field is available to be assigned issues on that JSW project. Check the Permission Scheme to make sure they are in the Assignable Issues permission. 

@Jon A - Did you get this resolved? 

Glad you got it working. And thanks for letting us know the reason. Hopefully, they have cleaned one of them out for you. 

Great! Glad to hear it is resolved. Please click on the Accept Answer button above so we can close this one out. 

Hi Nidas - Welcome to the Atlassian Community! You can try creating another board that uses a filter that includes both projects. See guidance here: https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

So that's the problem. Go to the permission scheme and then the permission helper. Then put in the information for the Set Security Level permission and see what it says. 

Hi Jamien, Is the Sub-task issue type in your Issue Type Scheme for that project? Here is more information: https://support.atlassian.com/jira-cloud-administration/docs/configure-sub-tasks/

Okay, so looking at the bug that Trudy posted, make sure the Category field is not on the Create screen. This happens with the Resolution field sometimes also. Also, be sure to go ahead and open a support ticket and let me know if affects you and site the bug number. 

Ah, maybe make sure the Security Level field is on the Create and Update screens for the project. Also, see if you can Create an issue with the Security Level or update an existing one. 

Can you share the rule that you have built along with the details of the Edit issue for that field?

Are you included in the security level you are trying to set it to? If not, add yourself there for the short term. Refresh again the rule, and see if you can add it then. If that works, you can get it saved and tested and then remove yourself from the security level. 

No, the functionality between the two project types is very different and that functionality is not seen there, then you can't do it unfortunately.