Stefan Salzl Community Champion

@Alex Holy crap!!! I´m so sorry.....it DOES happen on my site too. I just wasn´t aware of it :o :o Thanks for letting me know. Really much appreciate this. Best Stefan

As (i guess) your initial question was answered would you please consider to accept the answer in order to mark this case as solved and make it easier for other users in need of help to find soltuions? Thanks in advance. Best Stefan

Hi @Vincenzo Ciaravella , Is there any feedback on the suggested solution? Could that be tested already? In case the solution works please consider to accept the answer in order to get this question marked "solved" and make it easier for other users to find solutions to their problems. Best Stefan

I can´t really explain this behaviour. 1 thing i could suggest is to open the 2 test executions, open the history (at the very bottom) and take a look if the creator is the same in both issues or if there has been triggered any "hidden" automation. In case the behaviour keeps as it is I recommend to contact xray support…

Hi @Alex Borges da Silva , Even if there is no propper solution for bulk-function for workflows please let us know if your initial question was answered and if so please check the answer as accepted in order to mark this question as solved. Best Stefan

hi @Sivaruban Kanagalingam , Unfortunately I can´t think of a fitting solution here. I´m not sure if jira automation is sufficient to solve this tricky and kinda complex setting of issue-linking as this would need to nest several branches. At least my current knowledge is not sufficient at this point. Some more question to…

Hi @Peter Reiser , Could you take a look at my latest suggestion/documentation? Your feedback would be highly appreciated. Best Stefan

Unfortunately I can´t tell you as I am not proficient with Scriptrunner :-/ Best Stefan

Hi @Galina Kumykova , there is also a page in the Jira documentation regarding „working with epic statuses: https://confluence.atlassian.com/jirasoftwareserver0811/working-with-epic-statuses-1019393039.html Could also be solved with a workflow-post-function. Best Stefan

Hi @Abhishek_Ajmera , for further analyse could you please configure/add „logging action“ as described in one of the previous replies? And please if possible a screenshot of both the userStory and the expected epic? Does this happen with other epics too or only with a specific one? Best Stefan

oooooff.....haven‘t ever experienced that one :o that sounds strange. I know it‘s already been a long way but would i be possible to send a screenshot of the task issue you are testing as well as the test case? btw: does at least the automation works as expected? =)

I checked a few special characters but not the colon. In case your question is resolved please consider to mark the answer as accepted to mark the question as resolved and help other users who are in need of this information an looking for solution.

Is this behaviour reproducable? Did you try this again and it happens all the time? if so please document step by step. Could you please also provide screenshot from your automation rule? Best Stefab

Did you create the sub test execution out of the story (as described in my previous) or out of the testcase (you just wrote from test case)? THEN: changing back to the Story A, section "Test Coverage" click execute & choose "with sub test execution" Could you please show a screenshot of your automation rule? And if…

Is this only happening when the transition is done by the automation rule? Or even when you set an epic to done manually? Could you test this? In case this happens in both cases I would suggest to check the workflow if there is any post-action on configured. This is the link to documentation regarding Epic Statuses

You are welcome. It´s my pleasure to help getting things running ;) hmm....guess it "works as designed". Found that hint in another community post. Can´t really "explain" the logic of it either. Please consider to mark the answer as accepted to mark this question as solved and help other users to find fitting solutions…

Hi @Sahish , this could be achieved with Jira automation. As cloned issues automatically get linked (Clones/cloned by) on the creation a rule can be created that reacts on this type of issue linking and modify (clearing several fields) the recently created (clone) issue. Best Stefan

mkay....could reproduce the behaviour on my side. explanation (of my setting) there are 2 "kinds" of status for an epic: * workflow status * epic status Epics in with workflow status Done are shown in Epic Panel and/or roadmap. As soon as I set the epic status to "Done" the Epic disappears from both views. Could you please…

Are all the quick filters in the roadmap overview cleared? (not seen in screenshot)

Hi @Patrick Russell , Could you provide screenshots of an affected epic and also of the roadmap overview? Maybe there are some more hints that lead to a solution. Thanks in advance. Best Stefan

Awesome :) It‘s my pleasure ;) So happy we could get this working.

Awesome. Happy that this could be solved so quickly. Happy testing ;) Best Stefan

Hi @Sanjay Mukherjee , Within the test execution (where the test run itself is located) this can be tracked. The column "TestRun Progress" shows the percentage of completed steps (--> see screenshot) Hope this helps and fits your requirement. Best Stefan

You are welcome. Let´s give it a shot. In case this works for you please consider to accept the answer in order to have this case marked as solved ;) Best Stefan

Is there any just cause to work with tasks instead of subtasks? The described setting seems to me as the good practice in Jira to formulate subtasks for work that implements the story. Furthermore this eases a lot of things in regard of transperency (as well as for automation).

Hi @Sivaruban Kanagalingam , How is the dependency between those issues done? As these issues don´t have a parent/child relation how are the linked? That would be an important information to know how to call one issue from another one and finding an ideal solution. Best Stefan

@Curt Holley hahaha......so funny..... can´t stop lauging =D

Hi @Vincenzo Ciaravella , seems like working on my side: Have you tried to first use the .locale() and then the .format() ? following smart value worked for me: {{now.locale("fr").format("MMMM yyyy")}} Please let me know if this helps. Best Stefan

Hooooly moly..... :o :o how could I oversee this option??? OOOOMG...... Thank you very much @Curt Holley (even if I invested the whole evening in trying to find a solution for this haha) Well....learned a lot. therefore: it´s worth it. Thanks guys for that great solution and lesson :)

OK. I see. There is not really a "correct or incorrect" ;) If it fits the process of the company/team and does what it should it´s correct :) Sooo....here comes my (personal) suggestion that turned out as good practice several times in the past: * open a ticket that´s under test (for easier reference let´s call this "Story…