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

Cloning issues in the backlog view makes the original issue disappear

Thomas Urbanitsch_n3hv8c

Hi,

Since we moved to Jira Cloud i struggle with one reproducable bug when cloning issues in the backlog view of our boards (doesn't matter if the ticket is a sprint or in the backlog):

Select a Ticket
Clone it (either via the Details Preview or the Command Palette)

Actual:

After the cloning is done i refresh the page manually and it is now showing the cloned issue, but the initial issue is no longer displayed. If the page is refreshed manually i get a popup saying "Changes saved, but Issue not visible" with no changes in the list (no matter how often i refresh).

The workaround for seeing all my issues again is removing the ?selectedIssue part of the url and load again.

Expected:

The initial ticket is not disappearing.

Does anyone else have this issue or is there already a related report?

Thanks,

Thomas

Accepted answers

Bill Sheboy

Hi @Thomas Urbanitsch -- Welcome to the Atlassian Community!

I notice from the screen images you posted that this is a personal / private board, stored in your profile. It is not stored with the MP project you show. And, I just reproduced the result you observed.

I have noticed several challenges / limitations with personal boards, although I do not see this specific symptom listed in the public backlog.

You could work with your Jira Site Admin to submit a ticket to Atlassian about this symptom here: https://support.atlassian.com/contact/#/

You could also move the board to a project to eliminate the symptom.

UPDATE: I am now seeing this symptom for a company-managed project, Scrum board also, not with a personal board. I recommend submitting a defect for it.

UPDATE 2.0: Here is the open defect for this symptom, with a workaround: https://jira.atlassian.com/browse/JSWCLOUD-27351

Kind regards,
Bill

All comments

Trudy P Claspill

Hello @Thomas Urbanitsch

Welcome to the Atlassian community.

What type of project are you using? Get that information from the View All Projects page under the Projects menu.

Is it a Scrum board or a Kanban board?

Have you reviewed the History information for the original issue after the clone is made, to see if there is some change being made to that issue besides the clone operation?

Can you provide screen images from before creating a clone and after creating a clone, including the URL? You can obscure confidential information from the URL and issue data displayed on the screen. Please point out which issue was being cloned and the new issue created.

Thomas Urbanitsch_n3hv8c

Hi,

The type says "Company-managed Software", it's a ScrumBoard. In the original tickets history i only see the added link for the "is cloned by".

I just did see that my description is flawed -> the switch between the old one disappearing and the new one appearing happens after a manual refresh of the page. I will edit that in.

I can look into providing some footage yep.

Thanks for looking into this.

Regards

Thomas Urbanitsch_n3hv8c

Initial State:

Selecting the issue:

Cloning:

Clonging Completed:

I refresh the webpage (very briefly both tickets are visible):

I manually update the url and reload:

Marc -Devoteam-

Hi @Thomas Urbanitsch

I have seen this before.

I suggest to raise this at Atlassian Support, as this might be a bug.

I can also replicate the issue you encounter.

Bill Sheboy

Hi @Thomas Urbanitsch -- Welcome to the Atlassian Community!

I have noticed several challenges / limitations with personal boards, although I do not see this specific symptom listed in the public backlog.

You could work with your Jira Site Admin to submit a ticket to Atlassian about this symptom here: https://support.atlassian.com/contact/#/

You could also move the board to a project to eliminate the symptom.

UPDATE: I am now seeing this symptom for a company-managed project, Scrum board also, not with a personal board. I recommend submitting a defect for it.