Community
Q&A
Jira
Questions
Make time spent mandatory for group of developers

Make time spent mandatory for group of developers

Hi all,

In our workflow (JIRA 6.3.3), we would to ensure that when a developer resolves the issue, he logs Time Spent. However, since partners also can resolve issues, they are not obliged to record time. So, we would like to add validation like this:

If user in group <developers> then Time Spent cannot be null at Resolve action.

We tried JIRA Behaviors plugin, but it looks like cannot deal with Time Spent field.

What is the best way (Ideally if one can provide an example) to implement this check?

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote

I'd use the script runner to write a "validator" - it should be easy to pick out the current user's group (or role? Roles are better and easier to use than groups) and whether their update includes Time Spent data.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

You can have 2 resolve transitions, one visible only to "developers" and another visible only to "partners".

On the "Resolve" transition visible to developers, you can use a workflow validator to make sure "timeSpent" is not empty.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

You can use the "Field has been modified" validator or the "Field is Required Validator" validator, or both.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Um, that only gets part of the requirement (what about the type of user?), and can't handle "Time Spent" anyway.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Ooops! You are right, Nic. I didn't notice this detail! These validators worked fine on my workflows, but I hadn't the user restriction.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

We've all jumped down the wrong bunny hole at times ;-)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Reply

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Was this helpful?

Thanks!

TAGS

Community showcase