Yong Yang Community Champion

Hi @Emiliano Visioli The automation rule builder block is triger -> condition -> action. So we can't limit a condition before a trigger. Thanks, YY哥

Hi @Emiliano Visioli Welcome to our community. Could you please try Issue Type equals condition directly? Thanks, YY哥

Please show us your screenshot.

Hi @Els Vercauteren Welcome to our Community. You meant when clicking the card in active sprint, at the right, the issue detail page should show timespent (Time Tracking)? Thanks, YY哥

maybe the network issue. you could ask here and I will hep you

You don't have any permission to create a question? @Kamil Askerov 

Hi @Nick Haller I think you might misunderstand this question. Without any field ordering, the newly created ideas are always on the top while @Garrett Olsen expect they should be at the bottom of the board view. From my personal perspective, the behavior design in All ideas view is reasonal because we want the new ideas…

Hi @Gabriel Raubenheimer Thanks a lot for your detailed reply. Different user scenarios/cases need different solutions. I'd like to share my practice if you need a zoom call. Hopefully, there's a Chinese colleague with us talking 'cuz my English is not good ☺ Regards, YY哥

Oh, it's really weird. I can't get out the WHY. There's a workaround: a) create your first pipeline manually as the last screenshot shows b) copy the yml file content to the new one

1.Could u please show the status config for the right most column? as well as the story workflow. 2.When you move the stories to Done, they still appear in the last colunn, right? 3.Are you using company-manage project's scrum board? Maybe you could show some screenshots you suspect.

Hi @Jenny Luther Welcome to our Community. Do those 11 issues have the story points? Usually, when the stories with points are moved to the right most column, they will affect the burndown chart. Thanks YY哥

You're welcome. Your suggestion is valuable indeed. Please help take a look. Thanks @Tanguy Crusson 

Hi @amine mokaddem Welcome to our Community. Are you creating the pipeline yaml file like this? Maybe you could provide more info to use to detect the reason. Yml file codes? screenshots？ Thanks, YY哥

Hi @Monique Buis Welcome to our Community. I think you've asked a very good question. As far as I know, it's not feasible to implement it curently. Thanks, YY哥

Hi @Kamil Askerov Welcome to our community. Do you want to create a customred ULR field to store the link of this JSM ticket, which is invisible on customer portal? Here is the custom field type and the new field can be configured not shown on the portal. Hope it helps. Thanks, YY哥

Hi @Neta Rothman Welcome to our Community. It's feasible to copy issues across JSW & JSM projects. For example, when JSW issue is transitioned to certain status, trigger an automation rule to execute to create a JSM issue/ticket to edit its fields copied from trigger issue. Hope it helps. Thanks, YY哥

Hi @Vera Valshonok Welcome to our Community. In JSM Cloud, there's already a SLA field to implement your requirement: * Time to resolution (time duration from creation to resolved excluding non-working hours) If you want to define a new field, it's difficult to exclude the non-working days/hours from it. Hope it helps.…

Hi @Nina Welcome to our Community. You could go to the board sidebar Issues to see all the issues in this project. Or you could also go to top menu Filter to search all issues within the specific project. Hope it helps. Thanks YY 哥

Hi @Daniel Bermudez Welcome to our Community. It seems you're seeking the solution to connect JSW DC issues to JSM Cloud tickets. I know in JSW Cloud, there's the Application tunnels which can implement it. Hope it helps. Thanks, YY哥

Hi @Naman Kashyap My screenshot is from Jira Cloud. According to your screenshot of Jira DC, you don't have the specific user option. My suggestion is: a）Use group to include the specific users; b）Use project role to include the specific users, set those users in the project People setting. Hope it helps. Thanks, YY哥

OK. I just checked the creating issue Rest API with 400 bad request code: Please check those points, which may block you from creating issues in that project.

 Hi @Hala ElRoumy Thanks for your sharing. Automation for Jira (A4J) is a Jira App, which was acquired by Atlassian. And the rebradning name is Jira Automaiton, I think. Thanks, YY哥

Hi @Naman Kashyap Welcome to our Community. Please try update the Viewers as specific users of the Board filter. Hope it helps. Thanks, YY哥

Hi, I had an issue from automation log: What should we input for Smart Value of Summarize with AI action? Thanks, YY哥

Hi @Ian Lucas Please check the Scope of the automation rule in each project. You may need to make this project scope the same as that in which you're creating social media issue. Hope it helps. Thanks, YY哥

Hi @Ian Lucas Welcome to our Community. Please show us your automation rule detail (screenshot). Thanks, YY哥

Hi @serge calderara What's business scenario of this requirement? I may want to know firstly before providing my suggstion: 1.what's the rule of epic child tasks creation? only the issue type of Epic, you will need the same set of tasks to be created? 2.what's the rule of sub-tasks creation? based on the parent task's…

Hi @Mina Soultan Welcome to our Community. As far as I know, there's no automation execution limit for JSW DC. Thanks, YY哥

Maybe caused by this rule:

Hi @Consuelo Nicoli do you have two transitions to the status [To Test]? please go to [test disapproved] and see the condition (a screenshot) please.