Demand Management project / workflow in Jira

[Michael Surma]

Hello, I've just joined an organization that use Jira as tool for Service desk, general work tracking etc. We have a need to develop a demand management tool with a work flow. The tool would intake a demand. The demand may turn into a task or may become a project. At full maturity the demand, once approved, will become a project. 

I'm sure there is a lot of clarification needed. I wan to float this out there and get ideas as soon as possible.

Has anyone do something like this in Jira and or Confluence?

Thank you in advance

[Mark Treast]

Yes, it’s absolutely possible to build a demand management workflow in Jira that transitions from intake to project approval and tracking. Many teams handle this by configuring custom issue types such as "Demand" in Jira Service Management or Jira Work Management, and using workflow automations to convert demands into tasks or full-fledged projects depending on the approval path. You can design conditional workflows with approval gates, status transitions, and linkages to Epics or Projects in Jira Software. Integration with Pawa can enhance this even further by providing a streamlined interface or intelligent automation layer to collect, categorize, and route incoming demands efficiently. Confluence can support the process with templates for business cases or project charters linked to the Jira issues. This kind of setup is scalable and aligns well with portfolio-level planning.

[MarcSch]

Hi Michael,

we are in the same situation and want to use Jira as a demand management tool.

Current setup:

• Single Jira project with a portal view for customers (internal departments) to create demand requests. Demand could be a change (standard or complex) or a project, therefore we are using two different Jira forms.
• When an issue is created it is reviewd by IT (correct type? quality?...).
• For standard changes the issue is used to communicate with the department that created the issue. Subtasks are used to work on it (not visible to customer) with a defined workflow and DoD.

Future setup:

• For other changes including projects the plan is that the respective IT team creates tasks or epics (deending on size) in their team Jira projects linked to the demand request. For projects own Jira projects are created.
• One drawback is that we are not working on one issue and have to update status on two sides (IT project and demand portal). Sync apps are no option currently.

Regards

Marc

[Clark Everson]

Hi Michael,

Welcome to the community!

Does your organization have a Jira Admin? Many admins have done complex workflows like this, but the real trick to them is to keep them simple. Many people here could give ideas how to start a workflow like this but the issue comes when you need to make changes to it later, as those are often needed.

I would highly advise working with your companies admin. If your company doesn't have a instance admin, then I would recommend you look into one of the Atlassian Partners because the one problem with Jira long term is if you do these more complex things incorrectly there will be issues later on. Getting someone experienced for your instance will help scale the application properly versus having to do cleanup later. The cleanup of Jira is far more costly than doing it correctly rom the begininning. 

You can find partners here: https://www.atlassian.com/partners

Best,
Clark