I have downloaded the app from marketplace Workflow Rules Lite
When I select get started, nothing appears as it states? I do not have any options to create a rule?
Can I get some help ? I cannot set up what I need and as it is not an option to add a condition ?
@Michael Andolfatto I have ran into an issue with the validator and I am hoping that you can help me. I set up a validator for when the issue transitions to Ready for Development it should require entry in DEV LOE field or present the error DEV LOE is required:
Error when transitioning:
1. created ticket and starting status is needs definition, when attempting to transition to ready for deployment and inserting a vale in the DEV LOE field it still will not accept:
a. attempt to transition:
Entered value in DEV LOE Field and still not allowed to transition?
Can you please help me resolve this issue? I cannot make DEV LOE a required field at creation as it causes too many issues with automated rules and bug tickets auto generated from our automated testing tool that is integrated with Jira.
Thank you so much for your time in resolving this issue.
Hi @Trena Norcia ,
From what I can see your validator is set up correctly. My only guess from the available information would be if you have two fields with the same name DEV LOE and have validated against the wrong one - can you confirm if this is/is not the case?
There is only one DEV LOE field and one QA LOE fields this is so we can address the time needs separately. I had the DECV LOE field as a required field which is the need. But that had a negative impact across the board. Caused issues with the automated rules as well as caused DEV LOE to be required at creation when it is actually needed after the needs definition status (step). I cannot figure out why this is not allowing me to transition and require entry into the DEV LOE field.
This is a huge need.
I do not know where to go from here to get this to work.
Have you set up a transition screen on the Ready for Development transition?
Reading the rule description, it's validating against the field value being modified, so it would require you to change the value at the time of transition which would explain why your previous examples were failing.
Transition Screens will prompt the user to set one or more specified fields when attempting to transition an issue.
Transition Screens follow the same concept as the Screens in your picture- they are forms for one or more fields- but they don't need to be mapped to an operation (Create, Edit, View) like those ones.
To create one, go to your global configuration menu > Screens (you can press "gg" on your keyboard to open up a quick-search menu alternatively)
Also be sure to view my previous note- if you keep the "field modified" validator, you may run into an issue where someone creates an issue, fills out the field, and then tries to transition the issue without changing the value since it's already set. The validation will fail in this case because it's checking that the field has been modified at the time of execution rather than just holding a value
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event