Comments
-
Hi Michael, You usually do not have to assign an app to a project, certainly not with apps that add workflow features. I suggest you try enabling all conditions one-by-one, so that you know which one does not work as expected. My hunch would be that the last one for some reason evaluates to true, thus allowing your issue…
-
Hi Michael, While Kian's approach with JMWE should work, it'd like to show off an alternative app, called Cloud Workflows, that you could use. It allows you to add conditions and validators based on Jira Expressions. In case there are more issue types than just the sub-task in your workflow, you'll want to test for that…
-
Hi Jakob, Just you are still looking for a solution and are open to other apps: We have just released Cloud Workflows which enables customizable validators/conditions in Jira Cloud. I am 100% sure your use case can be covered with it. The app is available here: https://marketplace.atlassian.com/apps/1220407/cloud-workflows…
-
Hi Tal, In case you are still looking for a way to have complex custom validators in Jira Cloud, there now is an app that enables this. It's called Cloud Workflows and allows you to use Jira Expression to create your validators. If I understand your use case correctly, it can easily be done in a Jira Expression like this:…
-
Hi Miik, I'd venture a guess that your authentication token does not work as expected and that you are not really logged in. The resource /rest/api/3/project/ is accessible anonymously, so if you're not logged in an http 200 with an empty list would be the expected result. (It's also deprecated so, you might want to look…
-
Hi George, I know, it's been a long time coming, but we have just released our app Cloud Workflows that enables customizable validators/conditions in Jira Cloud. It's available here: https://marketplace.atlassian.com/apps/1220407/cloud-workflows Full disclosure: I work for Jodocus, the Vendor who created this app. Let me…
