SAFe EPIC to Feature Translator for Jira

What about enablers? Not even to mention the level up in the requirements hierarchy...

• 

  Appfire

  Hi Tiago,

  The app is intended to rename the "Epic" into "Feature" and doesn't deal with enablers. Do you have any other reasons for such rating in scope of the existing app functionality? If you reach us at products@cprime.com, we'd be happy to discuss your use case.

  Thanks,Cprime team

We're having problems with this app properly translating the Epic to a Feature when using the Two-Dimensional Filter Statistics macro from the Confluence Tables and Filters add-on. More information is available on this post to the Atlassian Community (https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-to-work-around-Two-Dimensional-chart-JQL-query-with-field/qaq-p/2075976#M95096). Can Appfire update this add-on so it understands it is generating a complex JQL query and substitute the original field name instead? This would presumably require looking up global translations.

• 

  Appfire

  Hi Jan,

  We're sorry you're experiencing this issue. Could I kindly ask you to raise a support ticket?

  All the best,

  Iván García, Product Marketing Manager

Hello, I have installed the application and it works at first sight. Unfortunately, however, we have found some errors in the German translation: 1. on the project page in the backlog it says Feature, but in the mouseover the following text appears: "Show Epic panel..." 2. if you want to enter a filter in the issues, you have to enter issuetype = Epic, otherwise the issues will not be found. 3. if you want to carry out an XML export, the changed wording e.g. "Feature status" appears in the XML file in the custom field, but "Epic status" also appears in the same sentence. 4. if you want to change something on the board (Kanban or Scrum) and open the board menu, "Show Epic Panel", "Hide Epic Keywords" also appear here. 5. if you want to link a story to an epic, it also says that you can select epics here. Thank you very much for your reply.

• 

  Appfire

  Hi Martin,

  We're sorry to hear you're experiencing the issues in the German translation.

  We would like to address this issue and for that we will need to get more information from you, would you mind submitting a ticket so that our Support team can help sort out the issue faster?

  Thanks! Elena Kolesnik, Product Manager

Is it possible to use this plugin for some projects and not for some others? Currently it is a general setting so "Epic" is translated to "Feature" in all projects, but we need Epics in some projects so such project based selection would help us

• 

  Appfire

  Hi Cansu! We have been investigating this very feature (pun not intended), however, at the moment this is not possible. The issue with this is that for some of the translations we have to rely on Jira functionality, that is Custom field and Issue type translation is done by Jira itself. And it is applied globally to all screens across the Jira instance, including all projects and boards. In this context, if we attempt to apply translations by project we will need to get rid of or work around the base Jira functionality that we rely on and create an approach which will modify the UI values of the html by javascript functions and will be tied by the UI itself. And the potential solution could still be unstable and unportable across Jira versions.

  That being said, we are working on the alternatives at the moment, because offering something unstable and unreliable to our users is the last thing we want to do.

  If there's anything we can do to help, you can always reach us at products@anovaapps.com, and we'll get you covered.Cheers, Anova Apps team

We are using this and it's working fine. Good add-on

• 

  Appfire

  Yes! Thank you for your kind review Ran! We are so happy you enjoy using our app.

  Cheers,

  Cprime team