LiquidPlanner Classic Forum

Ask a Question
Back to All

JIRA use case

Posted on behalf of a customer. Original posting date 2015-01-19.

In speaking with a newer client, they are intending to have updates to estimates on many JIRA sub-tasks all feed into / roll up to a single LiquidPlanner task. They would anticipate having many groups of sub-tasks feeding to many tasks. I was having trouble conceptualizing how this might work via API - would it be possible for sub tasks to be updated with some kind of ID field that would allow them to all associate with one task?

Might this group be forced to consider an architecture where JIRA subtasks have a 1 to 1 relationship with a LiquidPlanner task?