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’.

2 years ago
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.

a year 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).

9 months 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.

3 months ago