Project

General

Profile

Forums » Open discussion »

Validation on issue tracker before closing an issue?

Added by kishen ratilal over 9 years ago

I love using Redmine for issue trackers and it has great user experience.

I would like to know if there is a way to validate, like a popup message before I close an issue if a category is not selected?

For example in the attachment, if I set the status as "Closed" and click on "Submit" on the bottom, I want it to alert me that I haven't selected a category or i shouldn't be able to close if a category is not selected.

Any advice or help is appreciated.

thanks
Kishen

2015-05-29_10-53-30.png (48.4 KB) 2015-05-29_10-53-30.png

Replies (5)

RE: Validation on issue tracker before closing an issue? - Added by Leonel Iturralde over 9 years ago

Hi,
Try using Administration -> Workflow.
There is a tab called field permission.
Depending in the tracker and status you can set which field are required or readonly.

RE: Validation on issue tracker before closing an issue? - Added by kishen ratilal over 9 years ago

Thanks Leonel.

I just tried that and it didn't seem to work. I was able to "close" my support ticket without selecting a category which i didn't want it to happen.

Here is what I did in the workflow. I have attached a screenshot.

Am i doing something wrong?

2015-05-29_14-44-51.png (43.5 KB) 2015-05-29_14-44-51.png

RE: Validation on issue tracker before closing an issue? - Added by Leonel Iturralde over 9 years ago

Hi,
Yeah just like that.
I did not tried myself. So I don't know why it didn't work I thought workflow was for that.

RE: Validation on issue tracker before closing an issue? - Added by Mischa The Evil over 9 years ago

kishen ratilal wrote:

I just tried that and it didn't seem to work. I was able to "close" my support ticket without selecting a category which i didn't want it to happen.

Here is what I did in the workflow. I have attached a screenshot.

Am i doing something wrong?

Leonel Iturralde wrote:

Yeah just like that.
I did not tried myself. So I don't know why it didn't work I thought workflow was for that.

Hello kishen and Leonel,

From my experience I can tell the feature should work like Leonel explains. Usually the problem kishen is experiencing can be explained by the fact that this is tested with a user account configured to be an Administrator, which makes that workflow/fields permissions are inherited. This is explained by Jean-Philippe in #11887#note-2:

Jean-Philippe Lang wrote:

But after I attached a role to my administrator user to that project, it continues to ignore that "required" field permission.

Currently, admin users inherits workflow/fields permissions for all roles. So if the field is not required for at least one role, it's not required for admins. But if you set the field required for all roles, then it will be required for admin users too.

This behavior for Redmine Administrator accounts is added via #2323#note-11 and also applies to fields permissions (read-only via #3521#note-5 & required via #703#note-53).

I hope this info might shed some light on the cause of the experienced issue.

Kind regards,

Mischa.

    (1-5/5)