Jira Automation: Transition issues from released version to the latest unreleased version?

[Adam Betz]

When I release a version from the UI, I am prompted with an option to move all unresolved issues to another version (or ignore them and leave them as they are):

I want to create some automation that will provide similar functionality. Currently, I have a rule created to run on a schedule (every 2 weeks) that will create a new version, and then release the previous unreleased version (the default options for that action).

I'm struggling at trying to figure out how I can query all issues with fixVersion matching the just released version, and then assign them the fixVersion for the newly created ones.

I tried to create a JQL Branching statement, but I don't seem to be able to use a Jira smart value in my JQL statement.

Any ideas on how I can expand my current rule to accomplish this? Or possibly, with the aid of a secondary rule that triggers on version creation?

[Nic Brough -Adaptavist-]

You will need to look at the application that is providing or creating your recurring tasks.

[Tom Lister]

Hi @Agris B.

If you want to write filter to show tasks in next calendar month try the JQL functions

startOfMonth() and endOfMonth()

are the issues identifiable by their Due Dates?

e.g. due > startOfMonth(+1) and due < endOfMonth(+1)

[Agris B.]

But currently these next month tasks not created, only done setup in old tasks.

When I open this old task, I see that next occurrence will be on 30.11.2018, and then JIRA will create task with due date in November.

But is it possible to see all these "next occurrence" by list of all next month tasks?

[Nic Brough -Adaptavist-]

You need to look at what is creating these tasks.

[Agris B.]

Sorry, but I little bit not understood..

How to understand "what is creating"?

[Nic Brough -Adaptavist-]

I don't know.  You have not told us what is creating the recurring tasks.

Jira does not create issues itself.  As you have recurring tasks being created, there is some person or process creating them.  You need to look at whatever is creating them to answer your question.

[Agris B.]

It's done by JIRA add-on Repeating Issues

https://marketplace.atlassian.com/apps/1213072/repeating-issues?hosting=server&tab=overview

[Tom Lister]

Hi @Agris B.

Looks like this plugin sets info on individual issues to control repeat and sets up its own custom fields to support that.

try searching for 'Next Occurrence' in the date range that will trigger the next repeats.

[Agris B.]

Not given such field "Next occurrence" for filters:(, only visible in individual issues.

[Tom Lister]

Hi

the plugin documentation has notes on searching these issues in filters. Check their options and see what works for your issues.

[Agris B.]

Thanks!

I found that is possible to use searcing and found all cloned issues:

codedoers.repeating.nextOccurrenceDate is not empty

, but not possible to see exactly occurrences dates and planned due dates in list