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; } } }

I have one action across 2 user stories, do I clone, duplicate or link?

Helena Ferguson

Hi All!

I am writing a few user stories and 2 of them will share the same action for our analyst, I don't want to confuse them so I want to be able to have just the one action listed under both user stories (the action is just data analysis but I need to capture in both user stories) - do I need to duplicate or clone the story from the original ticket and link to the new ticket?

What is the best way to do it?

Thanks all!

Accepted answers

Alex Koxaras -Relational-

Hi @Helena Ferguson and welcome to the community!

I would write the two different user stories and just link them with an appropriate link type. The link type is something that you have to decide as a company/team. What clones means to you, or what relates to means to you etc.

If I were you, I would place "relates to", since it might have a similar action, but it's not the same user story.

All comments

Alex Koxaras -Relational-

Hi @Helena Ferguson and welcome to the community!

If I were you, I would place "relates to", since it might have a similar action, but it's not the same user story.

Craig Nodwell_7eve9b

Hi @Helena Ferguson fully agree with @Alex Koxaras -Relational- create the two stories and link them. Again the usage of links their names and the inward outward relationships created between the tickets is determined by your organization. Relates should be perfectly fine.

Helena Ferguson

Thanks Alex! Appreciate the insight, definitely need to work on aligning these types of things within the business, it can be very scattergun across the teams!

Helena Ferguson

Thanks Craig! Appreciate the advice

Welcome!

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

Quick Links

Find more posts tagged with

jira-core

link

clone

duplicate