Clicking the link right or pull request tasks often not leading to task

[rod]

Hi,

We are relying a lot on pull request tasks to know what is left to do in pull requests and we often struggle to get to the task.

We click the link (chain icon) at the right of tasks but often we get a brief window appearance after which the window disappears and the "#comment-12345678" part of the URL also disappears.

We are working on desktops running Windows 10.

What we found out while trying to use the tasks links:

• Links work better with Firefox than Chrome and Opera.
• Clicking the address bar just after clicking the link icon often helps.
• Many tasks where the problem happen are on comments on "outdated versions" of files.

Are there any tips that could help us fight less with the task links?

Thanks!

[schnepper]

We are running into the same problem. Clicking on the task sometimes works, but not usually. The pull request in question is large (99+ files). Clicking on a filename and then on the comment icon (bubble with number) works, but then one has to page through the file to find unresolved tasks. Using Linux with Firefox. Tried private mode with extensions disabled, but the behavior was the same.

Has there been any work on this?

[Theodora Boudale]

Hi @schnepper,

I just found that there is an open bug report about the task links not working if in the PR settings the Load files option is set to Individually:

• https://jira.atlassian.com/browse/BCLOUD-22056

Do you have the same settings in your PRs? If so, do the task links work if you change this setting to All at once?

Kind regards,
Theodora

[schnepper]

Thank you for the info, Theodora. The PRs that I am having trouble with have > 100 files, so that explains it. It would be nice if this were fixed.

[rod]

@Theodora Boudale: FYI: In our case we are already using "All at once".

If that can help, we also have a lot of files (66) and many tasks (in one case we reached the 100 limit).

[Theodora Boudale]

Hi @rod,

I would like to ask a few questions to better understand the scope of the issue:

1. Is this issue occurring for multiple users working on different machines?
2. Does this issue occur consistently for specific links (e.g. the ones with outdated comments), or does it seem to be random?
3. Are users using the latest version of Firefox and Chrome? (Please note that Opera is not supported, supported browsers are listed here)
4. Is it possible to try using the latest version of one of the supported browsers and an Incognito/Private window, with all extensions disabled, and see if the issue still occurs?

Kind regards,
Theodora

[rod]

Hi @Theodora Boudale ,

Here are answers:

1. Yes.
2. Seems to be random but more often on outdated comments.
3. Yes for both Firefox and Chrome. But working with Chrome (an Opera which is unsupported) was too painful so now the team all use Firefox now.
4. Some of our team already use private windows and have the problem and others are not using them but face the same problem.

Thanks!

rod

[Theodora Boudale]

Hi @rod,

Thank you for the info. I would suggest generating a HAR file while reproducing the problematic behavior with Chrome so we can further investigate. The HAR file contains private data, so I would suggest creating a ticket with the support team and then providing the HAR file in the support ticket, as well as the URL of a comment that has this issue. If we have an open support ticket, the engineer working on your case will be able to access the repo and comment as well for further troubleshooting.

You can create a support ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Kind regards,
Theodora