nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best practice for using Jira Issues (User Stories and Sub-Tasks) on multiple Jira Projects

Thomas Jansen

We are creating a set of user stories that are being used by the development team to create the system. Our software is being developed for the Salesforce platform so when it is installed, it must be "configured" to meet the business specific needs which differ from company to company so, therefore, we will want to reuse the user stories on many Jira Projects.

The user stories that are developed for initial use on the development are very similar to the user stories that are used when the application is configured for a customer.

What is the best way to clone, duplicate, etc the user stories and sub-tasks for reuse on other Jira Projects?

What is the best (most efficient) way to capture the user stories and sub-tasks for development while also capturing the user stories and sub-tasks for a customer project configuration.

Comments

Michael Kinloch

I'm currently facing exactly the same problem.

I've just designed a hierarchy enabling us to maintain a seperate repository of Epics and stories to be reused across customer projects.

Will be testing it out next week to see if it's actually viable. 8f it works I will post the design.

Interested to see what comments you get back here to see if anyone else has solved this problem before.

Thomas Jansen

Micheal,

I havent seen where anyone has been able to solve this use case.

Did your approach work?

Michael Kinloch

Hi Thomas, got sidetracked last week at work due to some other priority issues. Will be picking it up again this week to implement the approach and confirm it works. I'm putting together a work flow in microsoft vision too to map out how it would work. Once I've confirmed I will share the flow.

Mike.

Thomas Jansen

Hi Michael,

Did your approach work to solve this use case? I am still looking for someone who was able to solve for this problem.

Michael Kinloch

Hi,

It would be a combination of both. Typically your stories are your placeholders for a conversation and relate to a piece of business functionality. Tasks tend to be more technical in nature.

Mike.

Ammar Hassan

Thanks @Michael Kinloch, We are finally going with approach as you said.

Eran Malovany_h5o31q

@Michael Kinloch

Sorry to jump into so late
was looking for something and find out this post...

when you mention above a combination of both, what do you exactly mean, do you use story to define "end user functionality" and link to the story multiple technical tasks? or you use Sub-tasks that comes out of the box to split the stories to multiple technical sub tasks.

trying to find the best match, so multiple teams on the same project can work on the same User story but still be able to see all technical work in the backlog, estimate it and drag to the sprint of the relevant development team...

Thanks so much !

Eran.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

project

agile

clone

sub-task

story