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

When I update and save a story it overwrites the epic and is saved to the epic.

Connie Dietrich

I go into a story, update the story and save it. The verbiage from the story then overwrites the entire description of the Epic and automatically saves the changes. I have to then correct the epic. When I save the epic it does not overwrite the story.

Extremely frustrating...

Accepted answers

All comments

Nic Brough -Adaptavist-

This is not something Jira does natively - issues are all separate entities and an update on one has no effect on others (ok, some calculated stuff, yes, but no field overwriting field on other issues)

You must have some automation or script added to your system that is doing this. You'll need to find and fix that.

Connie Dietrich

There is no script or automation. I think it was happening when I had 2 instances of Jira open and one had the epic and the other had the story open. I currently have only one browser open with the story I am working on in it and I have not see the issue re-occur. I know I used to be able to multiple stories open and updates to one story would not affect any other story that was open at the time.

This only started recently.

Connie Dietrich

If it helps I am in new view. It does not appear to happen in old view. But it is definitely a bug in Jira and not automation since under Automation for Jira it says 'no automations available' and 'none executed'.

Nic Brough -Adaptavist-

Ok, that sounds like the session data in the browser is getting confused. I'll try to be simple and just use tab examples, but it could be more complex. Imagine Tab 1 is opened and goes to the epic, then you open tab 2 and open and update a story. It is possible (although most sane browsers would not do this) that posting the data in tab 2 also cascades into a post on tab 1.

The next time this happens, I would want to trap which browser you're using, what sessions are open, and take a look at the history of the issue and the epic, to see what times, dates and accounts are logged against the changes made.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud