Populate features based on release vehicle?

[Johnny Ringo]

Why does Jira Align not populate Features based on the Release Vehicle?  So, we've renamed Feature as Jira Epic.  When these come from Jira they hae a Release Vehicle assigned but now I'm having to manually select a Parent Initiative Breakdown and Planning Increment.  Why can't it auto-assign those two bsaed on the Release Vehicle as they should always be the same?

[Runtporplaca_1]

Hi Dear

From vehicle inquiries to driver's license verification and traffic violation status, the RUNT (National Single Registry of Transit) provides access to vital data for both drivers and vehicle owners. But did you know you can quickly perform inquiries using only a vehicle's license plate? In this article, we'll explore everything you need to know to consult the RUNT by license plate and obtain the most relevant information efficiently and easily.

https://runt-por-placa.com.co/

[Sofia sena Plus]

I recently worked on a Jira workflow where issues were getting stuck in review. One solution that worked for me is setting up a custom automation rule that updates issue status based on conditions automatically.
https://sofia-sena-plus.com.co

[Waris Qazi]

That’s frustrating. If the Release Vehicle is already set, it should auto-assign the rest. Doing it manually every time adds extra work. It looks like a limitation of the website.

[ahmet.kilic@catworkx.com]

Hey Johnny,

you expect a way to automate the links of Parent Initiative and PI from release into feature?

quick answer: There might be multiple associations than one.

A release holds multiple features (your Jira Epic) and each feature might be associated with different initiatives.

On the other hand, I would ask you for your "implementation runway".  Do you create first Releases than Features or vice versa?
This is related to the automation direction from feature to release which is happening already in Jira Align.

I hope this helps.

Best,

Ahmet Kilic

Enterprise Agility Consultant at catworkx