John Funk Community Champion

Hi Eric - Welcome to the Atlassian Community! Can you explain a little more what you mean? Sorry, but I am not following your thought process. 

Hi Javier, You should be able to create a filter that that shows that and then share the filter with the super user. 

You might need to add the Defect issue type to the Issue Type Scheme being used by that project. 

Hi Mark - You can use Automation For Jira to take a stab at that. You might need multiple number type custom fields though if you need to convert a string to another number first. 

Hola Alvaro - ¡Bienvenido a la comunidad de Atlassian! Hay un par de cosas que puedes hacer. Una es modificar el filtro de la placa para que solo muestre Epics. Entonces, en su filtro, agregue lo siguiente antes de ORDER BY y issuetype = Epic O puede editar el subfiltro en la parte inferior de la configuración del tablero…

Hi @Phionah Kyasiimire - Welcome to the Atlassian Community! Actually, a sub-task is just an issue type as well. AND, your Defect issue type is probably already created as a sub-task type of issue type and not a standard issue type. If that is the case, then you can create the Defect just like you do a sub-task. 

Sounds like you need to make some Arroz Con Leche or some rice pudding to me!! Then you could even drop it off with a neighbor to bless their day. :-) Kinda wishing I was your neighbor right now lol

Hey Riki - Looks like Ron will get you fixed up. I think you will enjoy the feature. :-)

You should put in a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Understood. I will send a note to Atlassian so that they are aware. 

Hey Samantha - we definitely need more information in order to help. What exactly are you trying to do that you can't right now?

You should create a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Hi @Giorgio Crosali - Just curious, but why would you want it removed? 

Hi Joyce - Welcome to the Atlassian Community! Take a look at this early post I made to see if it helps you. https://community.atlassian.com/t5/Welcome-Center/Research-The-Project-Types-Before-Committing-To-Early/m-p/1611682#M4295

Hi @Waqas Aleem - Do you have a Validator on the transition to Done in your workflow? 

Great! Glad you were able to get back what you needed. 

Hi Marcin - Welcome to the Atlassian Community! You could consider using a custom field with cascading values type, but that won't work if you want the first field to have multiple selections in it. The only way in Jira Cloud to come close to that would be to use a third party add-on such as ProForma Forms. 

Oi Fiorella, Dê uma olhada em suas Configurações pessoais para ver se as caixas foram marcadas primeiro. Clique no seu avatar e selecione Configurações Pessoais. Além disso, você pode considerar o uso de um painel com um gadget de fluxo de atividades para ver as atualizações sem precisar receber um e-mail. Então você pode…

Hi Dan, Use the lookup function in Automation For Jira. See that section in this document: https://support.atlassian.com/jira-software-cloud/docs/automation-actions/ You can also see more guidance here:…

Gotcha. I would assume that means you are stuck right now. Hopefully, there will be additional options coming, but who knows when. 

I am not exactly sure of what you are expecting the output to be, but, yes, you should be able to do that - give it a try and see how it goes. 

Hi Emily, I know they are rolling out changes now to allow Next-gen workflows to be edited. Have actually tried to do that yet? 

@Simmo - See above

Hi Antoine - Welcome to the Atlassian Community! Just the fact that it lets you create a Sub-task from the Epic screen seems to be a bug to me. I would report this via Atlassian Support: https://support.atlassian.com/contact/#/

Hi @Himanshu Nanda - I can't imagine the system will let you post a comment in the name of someone else. That seems like it would violate some security ideas. 

Hey Matthew - your last condition is going to process at the same time your branch is going to process since they are in the same level. Your re-fetch is on the branch and not the main level so the last part will happen probably before the re-fetch even happens. You might want to pull the last part our and do it as a…

Hi Erika, I have not tried that before, but maybe try this: <a href="{{issue.toUrl}}">{{issue.customfield_10014}}</a> Also, you do not need to tag adaptavist for Automation posts in Community is it is a different too. 

I think this is a Beta project that Atlassian is working on. It might have shown up in your instance briefly as a mistake. I will pass along to Atlassian your interest in the functionality. :-)

If that takes care of your need, can you click on the Accept Answer button above so we can close this one out? Thanks!

Hi Phil, You need to place a Validator on the transition to the Resolved status to make sure that the 3 fields are populated. As Jack says, you can't and don't do that with Automation.