Craig Nodwell_7eve9b Expert

@Randy O'Neal been breaking this everyday since the start of the month. I'm starting to feel like a tester with my purpose of breaking my as you put it "Like-o-Meter" A Tree Should Be Planted For This

Calming even now. A Tree Should Be Planted For This

Just a couple of guys watching those dancing Mounties. Also in the woods. Let's plant a tree for these guys too

And here's some dancing Mounties... AhYup in the woods. A Tree Should be planed for this

That small patch of woods, is still there all these years later. Some rich benefactor saved the land and had it turned into a park, maintained by the city of Toronto. For that I am grateful, those woods held many firsts as I became a teenager.

@Summer Hogan Great suggestion! A Tree Will Be Planted For This A Forest Will Be Planted For You

what are the field types?

:) I was referring to where in the Behaviour you are placing this.

Hi @Kha Hoang Go to you workflow, find the transition, go to validators, take the sciptrunner simple scripted validator. Put your string above in custom_field1 == 'No' || (custom_field1 == 'yes' && custom_field2 != "null"

Hi @Robert Bromley welcome to the community. Are you applying this to the field or as the initializer ?

Amazing what we hold in our hands.

Moose country

So different than what we have here in Canada

Read the entire book right here!

Fresh

Five

Peaceful

And now for 10 pictures of trees. A Tree Should Be planted for this.

I'd have to say my favorite memory is dessert.

you could also follow that example closer and put a validator on the custom field based on user role for the create transition or a looping transition with a condition on the user role and the value being null or something along those lines.

I'd create a fragment for the users based on role with permission who you want to be able to populate the new values, trigger a pop up input screen with a custom field, grab the updated value from that custom field and update the select list. That would be my approach. Hopefully that will get you started at least on…

We're getting closer. 1000 a day to keep the parking lot away

Hi @Va man out of the box jira no as mentioned you have to be a jira admin to add/modify/delete custom fields or the values in a select list. You could probably come with an automation through scripting to do what you need. Do you have any plugins available, like scriptrunner?

@David Fischer true my solution does not include workflow updates just the scripts that drive their post functions / conditions / validators... and I'm coming from a Server/DC perspective. @DevOps if JMWE allows your scripts to be saved as files then they can dropped into the /var/atlassian/application-data/jira/scripts…

Hi @DevOps welcome to the community. We use scriptrunner in our instance, it allows us to apply our workflow customizations to files. We've tied our changes around common build processes, where we modify in the version control system, this triggers a build job that grabs the files and drops them to a script directory in…

Hi @Sowmiya Srinivasan this is very doable. However you'll need to modify the workflow to not allow all transitions to all transitions. Or you can put a condition on each of the transitions not allowing the rejected status. 

< 14000 to go. Wooo A Tree Should be planted for this.