Stefan Salzl Community Champion

Hi @Anna Lucovsky , I see :) Sure will find a solution to this ;) There is one thing in your first screenshot that kinda confuses me: It shows one testcase in the list that says passed but the overall execution doesn´t show any passed part but all 81 testcases in "to do". Could you please who the whole testplan issue…

Hi @Luis Dominguez This example of an automation rule will always be triggered when an EPIC issue is updated. If this condition is fullfilled all stories/issues in the epic will be edited and inherit (in this case the value of the field "Country") from the EPIC (see screenshot) There might be some further refinement of the…

Hi @Luis Dominguez , from how far I got your requirement I think this could be done with JIRA internal automation. Just would have to specify the use case more in detail: * when/what exactly should trigger the update? * Could you describe the scenario like kind of "given - when - then"? Best Stefan

Hi @Anna Lucovsky , From your screenshot everything looks fine (unless that there are no tests listed during creating the execution). Did this work in the past and is now a new behaviour? What came to my mind is that there could be a correlation with permissions/statuses. There is a special setting for allowing executions…

Hi @Anna Lucovsky , Please ignore my last answer. I just saw that you mentioned the "all tests" in the first screenshot. Sorry for the confusion. Best Stefan

Thank you very much @Anna Lucovsky There should be a setting when clicking the "create execution" button regarding which tests you want to have in the new test execution (all, only a certain test status,....) * So when you click "create execution" do you see something similar to this: * and if so: which option did you…

Hi @Anna Lucovsky and welcome to the community, for gaining better insights of your problem could you please provide following screenshots: * your testplan (with the test cases) * the setting/configuration screen when you create the test execution * the test execution issue after creation Thanks in advance. Best Stefan

Before change: After changing Field "Stage" in EPIC (and automation rule): * * no changes made in "blocks" linked issue * changes inherited to issues with "implements" link * audit log of automation rule shows changes/changed issues (the changed issues are those linked with "implement")

Hi @Peter Reiser , if the link you provided here is the same you are looking for then I got you completly wrong. My understanding was: * There is an Epic A * Story B --> "implements" Epic A * Story C --> "implements" Epic A * Story D --> "blocks" Epic A * field values from Epic should be inherited to linked issues but only…

Hi @Peter Reiser , As mentioned before I just tried to reproduce some scenarios that might fit your description/requirement: * "Issue update" trigger * "Issue linked" trigger Looking forward to your reply. Best Stefan

Hi @Peter Reiser , I was just always try to know the whole specification and details on a functional level to then find a solution on the technical side (the same as I do in software development). Therefore I´m not quite sure my thoughts fit the requirement but I´ll give it a shot: As you mentioned your trigger works: did…

You are welcome Ben :) Sharing is caring and by trying to figure out solutions with my current experience I always learn a lot too :) So this is a win-win ;) Looking forward to hearing from you how it works ;) Best Stefan

Hi @Sachin Manjaiah , could you show a screenshot of your issue? Are those fields 'custom fields' ? I created a rule to kinda reproduce your requirement with the priority field: given: issue value changes in field 'priority' when: new value is 'highest' then: edit issue --> set Epic Link to <anyEpic> (eg. JT-58 in my case)

Hi @Benjamin Beach , there is a really good community entry regarding linking: https://community.atlassian.com/t5/Jira-questions/Issue-links-what-is-the-meaning-of-quot-inward-quot-and-quot/qaq-p/839095 soooo......I just created an example for the linking of "blocks/is blocked by" for some investigation and as this better…

Hi Ben, hmmm......it´s really tricky hahaha.....especially for the "relates" linking as this has just 1 direction and no inward/outward. In fact I´m able to do a copy successfully (also depends on which fields you want to copy). BUT: it really depends (and that could get "dangerous") which of the 2 issues triggers the…

Hi @Benjamin Beach , one more question from my side: should this rule be limited to the the case where link is set during creation of a new issue or should this always be triggered when linking is set (also in already existing issues) ? This might be an important requirement to choose the right trigger of the rule. Best…

Hi @Peter Reiser , Sorry I´m still not getting it in the Jira context. What exactly is the trigger? like: "When we update the epic-issue/when we do a certain update/action in the epic issue...." and the furthermore what should then happen: "....then all of the stories that are linked in this epic with "implements" should…

This is a bit missleading. The activity in the TestRun says "the assignee of THIS test execution" --> which means the test run. I just tested this in my instance (see screenshot). Could you please also provide screenshots for better understanding? Best Stefan

Hi @Benjamin Beach , Destination / Source depends on the linking goes inward or outward from the issue you are creating: means: if you create task B with link "causes Task A" --> Task A is the destination/Task B the source if you create task B with (inward) link "is caused by Task A" --> Task A is the source/Task B the…

Hi @Peter Reiser , could you please give a description how the use exactly looks like (like kinda step by step what should happen to which issues, which issue/level triggers the rule)? I would like to better understand the use case in order to provide a solution that really covers the requirement. Thanks in advance Best…

hi @Gama, Márcio ok that seems really strange. Is it completly empty? it doesn´t even tracks that there has been a re-assignment? Best Stefan 

Hi @Kiran Khan , As there cannot be string replacement in internal bulk-change i see 2 possible solutions here: 1. JXL-Plugin - table structure issue editor that allows bulk changes similar to excel…

Hi @Willian Stigliani Did you see any issues before? As you mentioned in your very first sentence you are using a custom workflow: If the standard/former used workflows are changed the new statuses need to be mapped to the columns of the board. Any status that is "unmapped" cannot be shown. Please go to board settings,…

Hi @Alex Bryant , as you already mentioned I guess that´s the point that you "activate" (by toggling) 2 filters to the same entity. If this is really a needed and often used scenario is there any conflict in creating another quick filter just for that special case (with a jql covering covering both status) ? That seems to…

Hi @Gama, Márcio and welcome to the community, Couldn´t reproduce the behaviour on my site (cloud) and cannot get a hint of a cause. Did you check the "Activity" section within the TestRun? Any changes that were made in the issue should be logged there (like the history of issues). Maybe this gives a hint who, what or why…

Hi @Ignacio Amoros ´, I got that (from a technical perspective). I´m kinda asking the concept behind it and why you would like to automate this level within jira. - how often are test-sets created? (as the concept of testSets in jira xray is mostly meant as a container of test cases so I can quickly create a test execution…

Hi @Nofar Ben Kereth , there was an article similar to your problem. Maybe this helps (search for 404, there was a suggestion of a community member with this problem and how they solved it): https://community.atlassian.com/t5/Automation-articles/Mention-someone-directly-in-Slack-via-Jira-Automation/ba-p/1528605 Best Stefan

Hi @Jignasha , the "create branch" option is only available with bitbucket (see documantation page): https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/ Best Stefan

Hi @Виталий , what @Mykenna Cepek wanted to explain is that the scope of an automation rule limits its "area of operation". It also limits where linked issues will be searched (in this case it´s a single project scope rule and therefore will only look for linked issues in the selected project and furthermore will not…

Hi @Akshaj Dave according to the xray marketplace page and as I experienced in the past there is only a free trial version for 30 days. After that you have to subscribe a paid version (see pricing site of xray). https://marketplace.atlassian.com/apps/1211769/xray-test-management-for-jira?tab=pricing&hosting=cloud As far as…