John Funk Community Champion

Se você estiver usando um projeto gerenciado pela empresa e criando ou editando um fluxo de trabalho para esse projeto, deverá ver apenas um status com esse nome. Você pode compartilhar as etapas exatas que está seguindo para criar o novo fluxo de trabalho?

Again, you can link issues but not projects. Not sure if that helps you or not. Good Luck!

ão, é baseado em status reais que você tem em sua instância. Que problema está te dando?

Hey @Mark Faddoul I assume you are no longer having this problem? Can you add an answer that was your resolution so we can close this one out? 

I don't think you will be able to do it using only Automation Lite then. 

Se forem projetos gerenciados pela empresa, você não deverá ver várias instâncias com o mesmo nome de status. Suspeito que haja alguns status com o mesmo nome de alguns projetos gerenciados por equipe. Então, você não pode realmente excluí-los porque eles não são realmente duplicados. Existe alguma coisa que está impedindo…

Post functions fire after something has taken place. Calling a transition screen has not completed any function, therefore, there is nothing that has taken place to cause the post function to fire before showing the transition screen. 

Hi @Vivek Challa - Welcome to the Atlassian Community! What do you mean by “match”?

Hi @chowin21 Nope, it applies to all licensed users of that product, regardless of how many actually use it.

Hahaha - thanks for keeping me in line

Well, not sure what I’ve done to disappoint you. But I’m sure it won’t be the last time either. 😊 yes you are correct in that your work management is really just a rebranding of Jira Cloud Core with some new and really nice features added. and yes, the board is still very limited. The set length of time for cards to appear…

If it's not firing, then I would check the Rule Details to see if you have the box checked to Allow other rule actions ...

What's not working? Can you share the audit log? 

Hi @nesrineZ - Welcome to the Atlassian Community! This is not going to work as you have it setup. You need something more defining for which issue needs to move - maybe a specific type of issue link or a particular field value for the issue that needs to transition. 

Great! Glad it is working for you now. 

Hi Julien, Not sure that I completely follow your scenario, but you can't populate the values in the screen on the fly when opening a transition screen if that is what you are seeking to do. However, you can create an automation rule that will auto-populate the due date based on the criteria you mention. 

Can you share a screenshot of one of the Initiative level issues? Also, when you say the automation does not work - what does that mean? That it doesn't fire? It gives you an error? Or it fires, no error, but it doesn't do what you want it to do? And can you share a screenshot of the audit log for that transaction? 

Hi Vaishali, In my opinion, it is mainly to assist with creating Advanced Roadmaps using the Premium subscription in Jira. 

Hi Farhan - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see if the email address was blacklisted on their side for some reason. https://support.atlassian.com/contact/#/

Você é muito bem-vindo.

Hi Parsa - You will need an add-on such as ScriptRunner or JMWE. 

Hi Martin - Welcome to the Atlassian Community! I would try that same query in the Advanced Search function and see if it yields the results you are looking for. Also, when you look at the board itself (not the Backlog) are they ordered correctly there? Just remember that the board filter will affect the entire board - not…

Hi LiJiao - Welcome to the Atlassian Community! There might be a way to do that using the API, but I don't have the knowledge of the details. You would probably have it all done manually by the time you figure out if there is another way or not. 

I would give someone from Atlassian another day. If not by this weekend, maybe we can engage them on Monday. 

Hi Kristine, Another option is to create a dashboard with an Activity Stream gadget connected to the project. Then every user can go see all of the updates at their leisure as often or as little as they like. And they don't have to deal with TONS of emails. 

Great - then you should have already identified what that issue link relationship is. Probably blocks/is blocked by or depends on/is dependent upon or something like that. 

Well, I have to disagree with you in regards to the Done category. The category designation refers to items that have reached a resolution and no more work will be done. This might be because it was indeed completed. Or it might mean that is canceled or aborted or abandoned or for whatever reason it was decided it would…

Andrew - have you already added a level above Epics yet? Such as Initiatives? 

https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

Ah, I think I see it - the Linked Issues field is for an actual issue key like ABC-123. I think you are looking for the issueLinkType field, which I don't believe is available in the Value field condition. You will need an add-on such as JMWE or ScriptRunner to be able to do that.