Webhook JQL on specific field updates

[ggol...@zendesk.com]

Hi,

I'm trying to register a webhook that would only trigger if certain issues fields are updated. Those fields could be default system field but could also be custom.

I found this https://answers.atlassian.com/questions/272815/jql-issue-changed-by-user, which suggests that this could not be done before but I was hoping that things have changed since 2014!.

I have also tried filtering by specific user, which also doesn't work, e.g. issue changed by myuser

Is this just not possible at the moment?

Thanks.

Grigori

[Einar Pehrson]

Hi Grigori,

I was able to accomplish this partially by using this JQL filter.

assignee CHANGED AFTER -1m

This prevents me from receiving a jira:issue_updated webhook whenever any fields aside from assignee is changed. There are two limitations though:

• The CHANGED operator can only be used with a set of system fields.
• You will continue to receive webhooks for updates to the issue as long as it matches the JQL filter, i.e. during a minute following a change to the assignee field in this case.

Cheers!

Einar

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Einar Pehrson]

Hi Gregori,

another approach, less performant, but potentially covering all kinds of fields, would be to store the last value your add-on has seen for a particular field into an entity property and use a JQL filter where the issue field and the entity property are non-equal. You could even use an entity property extraction to store several field values in a single entity property.

Cheers!

Einar 

On Dec 30, 2016 16:28, "Einar Pehrson" <epeh...@atlassian.com> wrote:

Hi Grigori,

I was able to accomplish this partially by using this JQL filter.

assignee CHANGED AFTER -1m

This prevents me from receiving a jira:issue_updated webhook whenever any fields aside from assignee is changed. There are two limitations though:

• The CHANGED operator can only be used with a set of system fields.
• You will continue to receive webhooks for updates to the issue as long as it matches the JQL filter, i.e. during a minute following a change to the assignee field in this case.

Cheers!

Einar

On Thu, Dec 22, 2016 at 12:53 AM, ggoldman via Atlassian Connect Dev <atlassian-connect-dev@googlegroups.com> wrote:

Hi,

I'm trying to register a webhook that would only trigger if certain issues fields are updated. Those fields could be default system field but could also be custom.

I found this https://answers.atlassian.com/questions/272815/jql-issue-changed-by-user, which suggests that this could not be done before but I was hoping that things have changed since 2014!.

I have also tried filtering by specific user, which also doesn't work, e.g. issue changed by myuser

Is this just not possible at the moment?

Thanks.

Grigori

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsubscri...@googlegroups.com.

[Daniel Wester]

Tangental question - if I recall there was a limitation size wise on add-on properties when it was first launched. Is that still there or has it been removed (or was it just something I imagined - which is very much possible)?

/Daniel

[Jon Mort]

Hi Einar,

How do you construct a JQL query that compares a field and entity property? My JQL foo is failing me.

Thanks

On Wed, 4 Jan 2017 at 01:45 Daniel Wester <dan...@wittified.com> wrote:

Tangental question - if I recall there was a limitation size wise on add-on properties when it was first launched. Is that still there or has it been removed (or was it just something I imagined - which is very much possible)?

/Daniel

--

You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jon Mort

Engineering|Adaptavist

[Einar Pehrson]

Hey Daniel,

yes, that limit (32 Kb) is still in place for all kinds of entity properties (add-on properties, JIRA entity properties, and Confluence content properties).

Cheers!

Einar

On Wed, Jan 4, 2017 at 2:45 AM, Daniel Wester <dan...@wittified.com> wrote:

Tangental question - if I recall there was a limitation size wise on add-on properties when it was first launched. Is that still there or has it been removed (or was it just something I imagined - which is very much possible)?

/Daniel

--

You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsub...@googlegroups.com.

[Einar Pehrson]

Hi Jon,

your JQL fu is probably better than mine, and I think I dreamt up that feature :/ There are a bunch of requests for similar ones on JAC.

Cheers!

Einar

On Wed, Jan 4, 2017 at 9:59 AM, Jon Mort <jm...@adaptavist.com> wrote:

Hi Einar,

How do you construct a JQL query that compares a field and entity property? My JQL foo is failing me.

Thanks

On Wed, 4 Jan 2017 at 01:45 Daniel Wester <dan...@wittified.com> wrote:

Tangental question - if I recall there was a limitation size wise on add-on properties when it was first launched. Is that still there or has it been removed (or was it just something I imagined - which is very much possible)?

/Daniel

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jon Mort

Engineering|Adaptavist

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsub...@googlegroups.com.

[Jon Mort]

Hi Einar,

Sadly most of those issues are closed. Comparisons would be really handy for us maintaining issue properties. We need to find issues that have been updated since we have set entity properties to keep them in sync.

Jon

On Wed, 4 Jan 2017 at 09:40 Einar Pehrson <epeh...@atlassian.com> wrote:

Hi Jon,

your JQL fu is probably better than mine, and I think I dreamt up that feature :/ There are a bunch of requests for similar ones on JAC.

Cheers!

Einar

On Wed, Jan 4, 2017 at 9:59 AM, Jon Mort <jm...@adaptavist.com> wrote:

Hi Einar,

How do you construct a JQL query that compares a field and entity property? My JQL foo is failing me.

Thanks

On Wed, 4 Jan 2017 at 01:45 Daniel Wester <dan...@wittified.com> wrote:

Tangental question - if I recall there was a limitation size wise on add-on properties when it was first launched. Is that still there or has it been removed (or was it just something I imagined - which is very much possible)?

/Daniel

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jon Mort

Engineering|Adaptavist

--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.