JETI: Initializing Due Date Field Question - Regex

[Raina Arjona]

I'm currently on JIRA 6.4.8 and using JETI 6.3.0.15

I need some regex help initializing the Due Date field. It doesn't seem to be working properly. My regex passes the test fine in jeti, but when I send test emails, with the data the field doesn't initialize.

I'm using the following Field Context and regex below.

If

Email Body

matches

(\W|^)Due Date:\s(\w+( \w+)*.+)(|$),

set

Due Date

with value

from Capture Group (2)

in new issues

The Due Date field is displayed on a ticket as dd/Mon/yy  which looks like 1/Mar/16 for example. I tried sending an email with Due Date: 11/Mar/16 as part of the email body, but the field does not initialize.

Is there an issue with my regex or is that field not able to be initialized via email?

I kinda feel like it's my regex. I had issues initializing a single select list custom field until I dialed the regex in properly.

Any help anybody would be able to provide me with is much appreciated! Thanks!

[Norman Abramovitz · Accepted solution]

There is an excellent free plugin called script runner that will do this task.

https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

https://studio.plugins.atlassian.com/wiki/display/GRV/Script+Runner

https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Transitionparentwhenallsubtasksareresolved

[Vishnukumar Vasudevan]

Thanks a lot Norman.

But, is there any work around in JIRA 5.1.3 ? I not that keen to install plugins.

[Norman Abramovitz]

Without a plugin or writing your own code, no.

I can understand your concern about installing plugins because it makes things harder to upgrade, could add instability and adds more complexity, but Jira is designed to be extended so not all features will be in Jira by default. I took some plugins off my environment for some of these reasons.

This is one of the few plugins I think you should consider using after doing your own homework.

1) How long has the plugin been around and being maintained?
2) Does the plugin author respond to issues found in his plugin?
3) How many users have downloaded it and what they say about the plugin?
4) How active is the plugin author involved in the Atlassian ecosystem (or Jira itself)?
5) Does the plugin solve your immediate issue and provide potential future solutions?
6) Is the cost of the plugin worth the functionality it provides?
7) Whatever other questions, I should have asked but could not think of at this time.

[Vishnukumar Vasudevan]

Thank you for your time.

[Deleted user]

I am sorry, not a validator in the workflow but a condition will do the trick. It will look like this:

All sub-tasks must have one of the following statuses to allow parent issue transitions: Resolved

[Carsten Beck-Astrup]

I think he asks for somekind of automation, so the parent issue automoves to a new status ie. all subtasks are approved then the parent can be moved to "Ready" automaticly.

[Vishnukumar Vasudevan]

Yup, thats what I look for. You have got any workaround ?

[Deleted user]

Build a validator in the workflow, which allows you to move forward, only if all subtask have reached their ``resolved state.

[Vishnukumar Vasudevan]

I need this to happen automatically. Also, I don't there an equivalent validator for this.