Best workflow for recurring optional steps and additional tasks with multiple clients

[Julien Borrelli]

Hello there. We provide one main service with up to ten optional and additional services, to multiple clients/organisations.

Wondering what whould be the best set-up:

- 1 jira core project per client, 1 big jira core project, 1 big Jira service desk project, 1 jira service desk project per client, or a combination of all this (1 big Jira Service Desk, and 1 jira core per client perhaps)

- workflow wise, should we set-up one main workflow, with multiple and optional steps, or instead one simple workflow for the main task/issue/service, and use sub-tasks for each aditionnal service with their own small workflow? Those are recuring tasks assiociated per client, so I would not want everytime to create one task, then add all the sub-tasks, that could become very tedious and unproductive. I also would like to use as little workaround as possible, like creating a template issus then clone it, again, tedious.

- is there a way for the clients to directly create their tickets, selecting which optional services they want along the main service? And if this is possible, is there a way to get the additional services choosen by the clients the previous time, to be selected for the next time they create future tickets?

I hope to find help. Thank you.