Sorry, we don't support your browser.  Install a modern browser

Jira Cloud - Support for Epic issue type rename in issuesInEpics()#22

L

In the implementation of SAFe we have renamed the standard Atlassian issuetype Epic into Feature.
Because of the rename the ‘issueFunction in issuesInEpics()’ search function throws the error ‘Failed to get issues in epic’.

3 years ago
1
C

the change to support a renamed ‘epic’ (such as ‘Epic (feauture)’ would be extremely useful for my projects since not easy/quick for Jira administrators at Lumen to rename the ‘Epic(feature)’ object back to the predefined ‘Epic’ without potentially affecting projects and also SAFe has Epic -> Feature -> Story hierarchy so the current named Epic(feature) is a better name than Epic xxx -> Epic -> User story. All your SAFe clients would greatly benefit from this change.

2 years ago
1
B

We renamed the “Epic” and need this extended support too (maybe you can just add an optional “EPIC_ISSUE_TYPE_NAME” parameter).

2 years ago
A

I was using Jira OnPrem for years and heavily relied on the Issuesinepics function which does not work in cloud. I get the message not avalabe yet. Will this be enable soon? If not I wil have to switch to a differeent product as he companys workflow is broken now that we are in the cloud.

2 years ago
1
A

Still patiently waitng for resolution on issuesInEpics(). The standard JQL “linkedissue in ( … )” works from a REST query without a problem. So, that should be easy enough to wrap around whatever previous stacked search returns. Having to keep our queries updated via an external tool because of this one small thing has become tedious.

a year ago
T

There is an Atlassian community post from 2021 answered by an Atlassian Team Member indicating that renaming Epics is acceptable.
https://community.atlassian.com/t5/Jira-Align-questions/Can-I-Rename-Epic-to-Feature/qaq-p/1792040

And there is an Atlassian community article posted by Atlassian about support for renaming Epics as part of Advanced Roadmaps, updated in Feb. 2023.
https://community.atlassian.com/t5/Jira-articles/Upcoming-Rename-epics-in-your-company-managed-projects/ba-p/1874726

With Atlassian advocating for renaming Epics, it is critical for app vendors to adjust to support this.

7 months ago
1
G
Changed the status to
Gathering Interest
7 months ago
J

We are unable to move forward with our roadmap to implement SAFe methodologies due to the potential failures of ScriptRunner functions. We are urging for the support of ScriptRunner when it comes to renaming Epics so that we as well as others can continue with our efforts to move towards Scaled Agile.

2 months ago