Jira Cloud Create a record Module | Community
Skip to main content
M
MariaRo6
New Member
May 5, 2025
Solved

Jira Cloud Create a record Module

  • May 5, 2025
  • 2 replies
  • 445 views

Has anyone used the Jira Create Record to create an Epic Feature assigned to a Capability? I have the Epic Feature creating part working, but not sure how to assigned that to a Capability. 

Best answer by Linzie_Posey

We successfully used a legacy JIRA Custom API Call module in Fusion to assign a Capability as the parent of an Epic (Feature). Since the parent Capability is static, we were able to reference its ID directly in the request body, eliminating the need to first search JIRA and map the result dynamically.

 

2 replies

M
Adobe Employee
monicacardosoAdobe Employee
Adobe Employee
May 12, 2025

Hi @mariaro6, 

 

Thank you for your question! I personally haven't used these modules to create an epic feature assigned to a capability. However, I have a general idea of how to approach this. 

 

You first have to find out how capabilities are set in your Jira. Navigate to the Jira Settings → Work Items → Issue Type Hierarchy to see how capabilities relate to epics or features.

 

Once you have that information, you can use a Create a Record Jira module in Workfront Fusion and look for a "Parent" field (sometimes called parentId or similar). If it’s not available directly, you might need to (1) use a Search Records module to find the Capability issue first, (2) get its issue key or ID or (3) reference that in the epic creation module’s parent field.

 

After assigning the parent, run the scenario with a test epic and check Jira to ensure that it's properly linked under the capability. 

 

- Monica 

    M
    MariaRo6Author
    New Member
    May 13, 2025

    Thank you, this was something we tried, but it seems we may have a permissions issue with Jira as we are not able to assigned to the Capability. 

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    August 29, 2025

    @mariaro6 Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!

    Kautuk Sahni
    L
    Linzie_PoseyAccepted solution
    New Member
    October 23, 2025

    We successfully used a legacy JIRA Custom API Call module in Fusion to assign a Capability as the parent of an Epic (Feature). Since the parent Capability is static, we were able to reference its ID directly in the request body, eliminating the need to first search JIRA and map the result dynamically.

     

      Terms & ConditionsAccessibility statement

      Loading footer...