A pop up with mandatory fields when these are not filled in

[Yael Dvorin]

Hey guys,

I made some fields mandatory fields to fill in, otherwise you can't change the status.

Are you familiar with a plug in that if mandatory fields aren't filled in, a pop up appears, with all the mandatory fields?

This way the user can fill in these fields in the pop up, instead of looking for each field..

[Hernan Halabi - Elite IT Consulting Group · Accepted solution]

Hello @Yael Dvorin you should configure the mandatory fields as such in a workflow transition and setup a screen associated to that same transition with all the mandatory fields on it.  No need of additional apps in cloud to do this.

[Yael Dvorin]

how though? can you walk me through how to do it?

At the moment i have this small pop up on the left bottom corner, that only says what are the mandatory fields.

I want a pop up in the middle of the screen that will give you the option to update the mandatory fields from there

[Hernan Halabi - Elite IT Consulting Group]

Is that happening when you try to create a new ticket? If so, you must edit the screen associated to the issue type you are using and add the missing fields there. That can be done from the screen tab from the project admin view

[Hernan Halabi - Elite IT Consulting Group]

If it's a validator the problem, do the following

Create a screen

Edit the workflow associated to the issue type with the problem

Look for the transition causing the errors.

Edit the transition and add the screen you created there.

Publish the workflow changes.

Sorry I can't send images to make it easier. I'm writing from my mobile.

[Yael Dvorin]

I'd appreciate some pictures when you are not from your mobile.

I think it would make it a lot easier..

Thanks!

[Hernan Halabi - Elite IT Consulting Group]

Here are some images, you go to project settings

at the workflow tab you edit the workflow associated to the issue type

Select the transition and click edit

Pick the screen you want to show during that transition.

Publish the changes and that should be it.

Hope it's clear enough now

[Yael Dvorin]

Thanks a lot!! I did what you said and it worked

one more question though, do you know if there is a way to somehow add the original estimate field to the screen as well? couldn't find it

[Nic Brough -Adaptavist-]

Original estimate is a part of the "time tracking" field - you can add that to a screen.

[Yael Dvorin]

Thanks:)

And is it possible that the screen would pop up ONLY if one of these fields is missing?

If everything is filled in i dont want it to pop up

[Hernan Halabi - Elite IT Consulting Group]

You could but I wouldn't recommend. For that you must have 2 transitions to the same destination. 

First one has conditions in place in order to be shown only if all fields are already filled and no screen assigned to it.

The second one is the one you have with conditions as well in order to shown if any of the fields hasn't been filled yet.

[Nic Brough -Adaptavist-]

No, transition screens are always presented to the user.

You could use parallel transitions though - let's say you have a field called "my field", which you want to be mandatory when going from status X to Y

Create two transitions from X to Y, with

• Transition 1: 
  • Condition: my-field is empty
  • Transition screen: a screen with my-field on it
  • Validator:  my-field must be filled
• Transition 2:
  • Condition: my-field is not empty
  • Transition screen: nope, don't need one
  • Validator: don't bother here either

[Yael Dvorin]

Thank you guys!

Will try it

[Yael Dvorin]

@Nic Brough -Adaptavist- @Hernan Halabi - Elite IT Consulting Group Why wouldn't you recommend this?

[Hernan Halabi - Elite IT Consulting Group]

If you start using this type of config, the maintenance starts to get more time consuming. Suppose that you later have to add one more field, you will have to change two transitions instead of only one just to do that. That is in the best of the cases that you know/recall that need to be done in two places instead of one as is in most of the cases. Now suppose you have that same behavior for 5 more transitions in that workflow. That's 10 more chances that a mistake is done on the future changes of the workflow. Then let's suppose that since is great for the end user, you had to replicate that behavior on other 5 workflows... I guess that by now you can notice that it's not a scalable solution.

In my experience if you setup this once, you end having it everywhere with all the implications I mentioned

[Nic Brough -Adaptavist-]

I agree with Hernan.  My "solution" works and keeps it as simple as possible for your humans, but at a cost of making admin harder. 

In fact, all solutions make admin harder, other than the really simple one - ask your humans to understand the process and hence knowingly choose the right thing.

[Nic Brough -Adaptavist- · Accepted solution]

How have you made these fields mandatory?  Validators or via field schemes? 

[Yael Dvorin]

validators

[Nic Brough -Adaptavist-]

Ok, I'll defer to Herman's answer, as that's what I would be doing too.