Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

The Curious Case of the Disappearing Defect

Interesting possible bug?

A file was added to the review as a diff. I moved the sliders to only select the latest revision so I could see all lines of code, and added a defect on line 8 (which doesn't appear in the diff).

When the diff is displayed, my defect appears at the top of the page. If I click "Edit" on the Defect, it disappears. The replies to my defect are still displayed. I have to change my selection so that I am looking at the whole file and the applicable line of code with the Defect on it in order to edit my Defect. It doesn't matter which revision I look at, as long as Line 8 is identical to the Line 8 I made the Defect against.

This also happens on when I have multiple revisions/commits added to a single review. As lines are changed, often in response to a defect, over the various commits, my Defects/Comments will disppear when I try to edit them unless I go to the specific revions/commit with the original/unchanged line of code that the Defect was made against.

I don't understand this "feature". What is the purpose for requiring me to change my selected revision/diff in order to edit an existing defect/comment? Is there somewhere that gets into the "nitty gritty" of how specific lines of code and defects/comments relate when it comes to display and edit, because this is not intuitive.

2 answers

1 accepted

0 votes
Answer accepted

What I finally figured out is that when I have more than one set of revisions on my diff, this will happen. Apparently the defect is tied to the particular revision/diff that it was made against. I still haven't figured out how to pinpoint which revision/diff owns the defect, but usually we can play with it until it stays when edit is clicked.

However, this is painful.

Please note that we edit Defects to change Defect Classifications, which is why displaying the specific line of code isn't necessary.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

84 views 1 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you