I manage a Now, Next, Later style Project Roadmap board (displays Epics from multiple Projects). We utilize a Custom Field to assign a Now, Next, or Later field within the Epic to assist us in reporting and other business documentation.
I am looking to set up an Automation from my Project Roadmap that, if an Epic is moved columns (ie, from Now --> Done, Next --> Now, Later --> Next), it automatically updates the Custom Field within the Epic to reflect the Roadmap columns.
If needed information, these columns do contain multiple statuses
Hi @Anna Luszcak,
Could be you have by now resolved your question, but since it is not conclusive from the thread here ...
It seems that you have more or less mocked Jira Product Discovery here to build a roadmap based from your epic backlog to some extent. Going forward, it may be useful for you to have a look at how JPD works and separates your product roadmap from your actual delivery backlog.
But having said that and where you are now - a working solution would be to use an automation rule based on the workflow statuses in your workflow rather than from your board columns. You will have discovered that there are no board column related triggers available, but you do have workflow statuses mapped to your columns.
So it should be perfectly possible to use a Work item transitioned trigger for your workflow and indicate e.g. the list of statuses you mapped to your respective columns to reproduce the now next later columns you have in place.
Hope this helps!
Hey @Anna Luszcak
This seems very interesting. Could you assist with a few screenshots? Mainly of the columns in use?
Is this now, next, later also used for statuses of the epics? Or not?
Thanks
Aaron.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please see the included screenshot of the Roadmap columns: Later, Next, Now, Done:
Within the Epic, we use a Custom Field 'Roadmap Horizon' as shown below:
We do NOT use Now, Next, or Later for the status of the Epics, nor will we going forward. It is not a viable option for our workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah I see, so you want the column to dictate what enters that custom field? Almost like a status mapping to each column?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct. It would be helpful if I could move an Epic to a different column, the Custom Field would adjust to reflect that, instead of having to manually assign. Hoping to shave off time from the manual assignment and reduce errors.
Big picture: Our company utilizes a Now, Next, Later (and recently completed) Roadmap for monthly reporting internally to relay progress and upcoming changes as well as a dynamic table that displays our Now, Next, Later Epics in a more visual manner for stakeholders so they can see what features and changes are upcoming as well outside of release notes. These reports and visuals are tied to JQL queries that refer to the custom field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As the board column are normally just a visual representations of statuses, it may be hard to trigger a field change if those columns are mapped to any statuses.
If your organisation uses Scriptrunner, that may have a way of doing it.
I will look into it though, without the use of Scriptrunner.
Thanks
Aaron.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anna Luszcak could you tell me the exact project type your roadmap project is?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.