Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.Details:-------org.apache.velocity.exception.VelocityException:

How to link an issue in a non-'next-gen' project to an epic in a 'next-gen' project?

Deleted user
October 29, 2018

We want to make use of the new roadmap features in a next-gen project. However we cant link issues to epics from other non-'next-gen' projects. From the next-gen project is seems you can only create new child issues or link existing ones already defined in the same next-gen project.


If we try to link the child issue from the project in which its exists then when you search for the epic it displays its name as 'unlabelled-KEY-01'. If you attempt to link to it then you get the error - Issue 'KEY-1' must be of type 'Epic

1 answer

0 votes
Boris Georgiev [Appfire]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 25, 2014

This issue seems similar to the following bug https://jira.atlassian.com/browse/GHS-11025 which is fixed in JIRA Agile 6.6. Which JIRA Agile version are you currently using ?

Rahul Savaikar
Contributor
January 19, 2015

Even I am using the JIRA Agile version 6.6.13 with the JIRA version 6.3.11 and facing a similar issue. Do you think updating from JIRA Agile version 6.6.13 to 6.6.51 will resolve the issue? Regards, Rahul Savaikar

Manjunath R
September 30, 2020

Hi @Boris Georgiev [Appfire] ,

We are using Jira 7.11 and we are facing this issue

Suggest an answer

Log in or Sign up to answer