Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using Confiforms to create JIRA Issue under an existing EPIC Edited

I am trying to create a new JIRA Issue under an existing EPIC.  But when I try to specify the Issuetype I get an error that the issuetype used is a parent issuetype.  Please help with the Rest API code to add a child issue under an existing EPIC project type.

 

 

Thanks!

2 answers

1 accepted

2 votes
Answer accepted

Figured it out.  You need to add the Epic link Field as key in order to create an issue under a particular EPIC

I believe it is the same as creating a sub-task in Jira - you need to specify the parent issue

See this question and the answer for the details 

No, JIRA will throw an error that the issuetype is of type Parent.  Tried that already, didn't work.

Can you share your findings then? So, others interested, will be “educated” :)

Yes, here is what is needed to make the issue creation within an EPIC project work:

 

{
    "fields": {
       "project":
        {
            "key":  "PRA"
        },
        "customfield_10830": "[entry.JID]",
       "summary": "Issue creation",
       "description": "This enables Issue Creation within EPIC",
       "issuetype": {
          "name": "PRA Requirement"
       },
      "assignee": {"name": "[owner]"},
       "priority": {"name": "Major"}
   },

 }
}

 Important field to note is customfield_10830 which refers to the "EPIC Link" field.  This is a custom field which will have a different number depending on how your JIRA instance has been set up.

The issue type in my case is a custom issuetype, but can refer to a standard issuetype within JIRA.  You need to specify the issue type which will get created under the EPIC hierarchy.

Thank you for sharing this, so the idea is to get the correct field used for "epic" links and set it to Jira issue key (corresponding to your epic)

Great!

That is correct Alex.  :)

Hey Guys, what do we mention in 

"[entry.JID]"

I have tried the name and number both of the EPIC but still getting the error.  

The "JID" is the field (name in ConfiForms) where they store Jira issue key (to be used as "EPIC")

Alex

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you