John Funk Community Champion

Hi Emre, You need to setup a variable and then use the value of the variable. See this other post that will guide you through that. https://community.atlassian.com/t5/Automation-questions/Automate-quot-Target-Date-quot-field-when-ticket-is-moved-to/qaq-p/2251838

О, ты не можешь. Задачи следует назначать только одному пользователю, поэтому в Jira не может быть двух уполномоченных. Вы можете создать настраиваемое поле, которое является многопользовательским полем выбора, и прикрепить его к своей задаче, если хотите.

Hi @Айгуль - my browser translator does not appear to be working very well. Can you provide more details or re-phrase your question? 

Hi Colleen, You should use the Approvers field that should already exist. If not, create one called Approvers, but do not duplicate that field if it already exists. 

Hi @N Galvez - Welcome to the Atlassian Community! For the Shipping Address field in the Project B creation automation, use this code: {{triggerIssue.Shipping Address}} Make sure the field name in the code is exactly as the custom field is created, including case. 

Hi William, There's a pretty good chance that you will lose the Parent Link capability if you downgrade. This is what it looks like in my non-Premium instance. 

You are probably going to have to ask Atlassian about why they don't make the Parent field available in Confluence for that. Please post back here with the resolution so that future readers will know what happened. Good luck! https://support.atlassian.com/contact/#/

It's a field in the database. I you create a filter, you can show the Parent as a column. 

Can you not use the Parent field for that? 

@Samuel Penn - You are not losing that ability - that's what the Summary field has always been intended to be. Having both a mandatory at create Summary field and Epic Name field really makes no sense. It just brings Epics in line with all other issue types in Jira for clarity. I wish this thing was rolled out yesterday!

Sorry, but I am still now following how you are pulling the issues into Confluence. Can you not just use the label field and pull everything with that label? 

That happens automatically when you create a sub-task. You would not be able to create one without identifying the parent. If you look at the sub-task you have created, you will see that is is linked to the parent story. I don't think you need this rule at all, unless I am missing something or not understanding what you…

Hi Keishi, What are you trying to Link to? 

You are welcome. And glad it worked!

Hi @Lina Marcela Almanza P_ I am marking Earl's response as Answer Accepted. Please let us know if you still have questions. 

Hi Keishi, Click on the words Current Issue in the Edit issue action. Then select to copy from the Parent Issue. 

Pretty sure that Sub-tasks are not show directly on the board as individual cards. The show as a field on the parent card on the board. So if a workflow ONLY has a sub-task issue type associated with it, it's probably not going to be able to show that. You should probably open a support ticket with Atlassian to get…

Hi @Vasundhara Verma - Did you ever get this solved?

Yes, this sounds pretty straight forward. Created a rule an Issue Transitioned trigger. Then add an If / Else block condition. For the first If condition, choose add condition then use Issue Fields Condition. Choose your checkbox field and the value of one of the 7. Then add a new action for Create issue and chose the…

Yeah, that one is beyond me. I suggest you open a support ticket with Atlassian to see what they say. Please post back here with the solution so future readers will know the answer. Good luck! https://support.atlassian.com/contact/#/

Hi George - Welcome to the Atlassian Community! Last I heard, you could not have custom fields that were mandatory in Jira for the issue to be created from Teams. It handled system fields only. But that was months ago. You probably want to open a support ticket with Atlassian to verify. Please post back here with the…

Excited about the filter improvements. Hoping we will be able to have more control in filtering Done items on the board!!

Really good stuff coming!

Thanks for sharing Summer - and best of luck on the surgery. 

It was definitely sadness that I felt in the reliving of the accident. I had no idea what had actually caused the initial crash so that was good information for me. It reminded me of the Space Shuttle Challenger accident. It's hard to plan for so many anomalies with something that complicated. It's also sad that initially…

Yes, just try to run the rule as a single project rule - only citing the triggering project. But then go ahead and create it in the second project and see if that works for you. No, there's not a way to do that real time with the trigger. You could do a scheduled trigger and run it once a day or a few times a day if…

Hey @Josreny Botardo - Just following up on this since it's still open. Did you ever get a solution? 

When the issue is created, it will automatically put the person who submitted the request into the Reporter field. There's no need to have a separate field to ask them who they are, the system already knows that. 

So, let me see if I have it. When an issue is transitioned to a particular status, you want a new sub-task created automatically based on the value(s) of a field. If there are multiple values checked, then multiple issues are created. Is that correct? 

It's really more about experience than anything. It's hard to read up on that and take a test without having used it much.