Stefan Salzl Community Champion

As far as I got it right: for example you have Request A and Request B. Request B is linked to Request A. Within Request A you click the manual trigger and expect Request B to be transitioned to the same status than Request A. The point is within your workflow issues cannot transition "globally" from any status to another…

Hi @David Gan , Could you please show the whole issue? Are those screenshot from the same issue within the same project? Which issue-types are the main/standard issues you want to create sub-tasks to? Are there any screen schemes or required field associated? Or any validator in the workflow for the create transaction?…

Hi @Evanthia Charalampidou could you please add screenshots of your procedure? I´m struggling with "where" this happens. Furthermore: What is the expected result? Is it usual linking issues to other issues (like "relates to" etc)? The purpose of the TestPlan issue is to plan test executions/activities within a…

Hi @Ashish Sarraf There is a whole bunch of add-ons/connectors in the JIRA marketplace. I do not know all of them so I would suggest to do a research/look into marketplace how this can be done. Best Stefan

Hi @Wafa SELLEMI and welcome to the community, Could you please also add a screenshot of the involved issues? That might make it easier to understand and analyze your problem/requirement. Best Stefan

Hi @David Gan and welcome to the community, For better understanding: Could you please specify your requirement in more details? * When does this happen? * Where are you trying to create a sub-task (in which issue/in which screen)? * Please also add screenshots for us to better analyze the problem. Best Stefan

Hi andre.gans@dominolaser.com , Is this still an issue or could you find a solution on this? I ran into this problem with cypress tests yesterday and found out how test executions can be linked to existing tests. Let me know if you are interested in some exchange. Best Stefan 

Hi @Evanthia Charalampidou , I´m a bit confused by following lines: However, there are some features that have no equivalent Tests and then In order to bulk link the equivalent tests Are they now equivalent to the stories/tasks that you linked to the tesplan? Or is this information immaterial for your requirement? Which…

Hi @Fense Ling and welcome to the community, assumed you have the permission to there is an "Attach" button when you open an issue (see screenshot) Best Stefan

Hi @systems-intern , for deeper understanding and analyze please consider to also provide further information in the form of screenshots of eg. issues, current automation rule,... From what you wrote at the end (the compare date regard 1st or 2nd half of the year): would the following solve that in an easier fashion:…

Hi @Adrian.Seiler and welcome to the community, first of all: is that a tricentis/tosca T in your avatar? 😉 I would suggest to edit the monthly automation rule to immediatly create/fill that field on creation (as far as I got it right this monthly automation rule already exists). a few quiestions to further specify the…

Hi @Jenn Molyneaux , From my point of view the rule in your screenshot looks pretty much how I would try to solve this. 3 points that came to my mind: * the condition in the branch: why are you checking if linked issue is in status "in progress" or "done"? That would cause the rule only doing the action ONLY if the linked…

hi @Mykenna Cepek , as I remember you as a community leader I would like to ask how to deal with this: I posted a question. This question was accidently created as duplicate of https://community.atlassian.com/t5/Jira-Software-questions/xray-error-importing-execution-results/qaq-p/1964872 I answered my question by myself in…

I found the solution: The very first time I imported the test results I wasn‘t aware of how results could map to already existing test cases (let‘s say „test A“ and „test B“ in this example). Hence new testcases were generated in status backlog („test C“ and „test D“). Even after editing the original tests (A & B,…

@Rajesh.Sundaresan Please consider to click "Accept" next to my answer in order to this issue to be marked as fixed ✌

Your guess makes sense to me. Still I´m not quite sure which event is "overtaken" by the other one (means: from a technical perspective --> when exactly is the create issue "fired" within jira? maybe the notification itself fires too early and would also be done later if automation rule is postponed with a makeshift…

Hope they also replace it on the documentation =/ as this one doesn´t work obviously. Was there any feedback on that? As your question is closed could you mark the answer as accepted to mark this case as solved and make it easier to find solutions for other users?

Please see the very first answer. The reporter himself added the answer after getting in contact with Atlassian support. https://community.atlassian.com/t5/Automation-questions/How-to-handle-multiple-actions-from-different-field-checks/qaq-p/1949361#M3381 Hope this is solving the problem. Best Stefan

@praveen rathore any feedback? Best Stefan

guess we are very close now :) I remember a question here a few weeks ago where this was exactly the case that a processing of a form action took longer than the trigger of the automation rule. I will go through my recent posts as I was part of that question/discussion and will let you know what I found. Best Stefan

okay. Are the issues created via form? 

Is this issue created in jira service desk? When is the email sent? is this also done by the automation rule? How is the rule continuing and what is the "refetch data" for? (--> I´m asking as the refetch would fetch data from the issue as it was at the point of the trigger). Could you try to run the rule without the…

Hi @Sanjay Mukherjee , I´m afraid there is no gadget that will show testRun progress (at least I don´t know of any and couldn´t find one). Sorry, this time I cannot provide a straight forward solution. Did you use the community search?? maybe someone already had this question before. If not you could create a new question…

You are welcome 🙌 Looking forward to your feedback if this could solve your requirement. Best Stefean

hi @Chaitanya B and welcome to the community, one way that comes to my mind would be to check this in "issue type schemes". This view will show you * which issue types are associated in which issue type scheme(s) * to which projects are these issue type scheme(s) associated (--> this will then answer your question) To see…

Hi @Julian and welcome to the community, I´m afraid I didn´t fully understand the whole use case from beginning to end. Could you provide a step by step description in a functional way (more from a flow perspective not in a technical or system way, just as you would describe somebody that is not familiar with jira). The…

Hi @Heering Ligthart As far as I know there is no "out of the box" feature for this requirement. What comes to my mind would be working with validators/post functions in your workflow (create transition) and/or automation rules when field gets edited afterwards (if possible at all). Hope this was helpful. Best Stefan

Wait....guess I found something that could be a feasible way: * Add a validator to your workflow for "Create" transition * choose the field that needs to be required * this will behave as follows:* type in "summary" in quick create line in backlog * by hitting "Enter" the create screen automatically opens * hint is shown…

What exactly and why is the "quick create" a requirement?? using the "quick create" is just a way of creating an issue. Is it really your requirement that the quick create has to be used or is it a requirement that an issue with some required fields should be created? Furthermore: What would the quick create scenario would…

hi @Magdalena Zhisheva as far as my knowledge reaches there is no option to configure that. My question here is: What avoids you to create an issue via the „Create“ button at the top? With this option you could configure the „create screen“ to have required fields. Hope this was helpful. Best Stefan