|
USA-FL-ZEPHYRHILLS Azienda Directories
|
Azienda News:
- How to follow duplicate issues in Jira? - Atlassian Community
Let’s take the case when we need to check for duplicates every new issue with the full match by Problem and Client fields (a client has a repetitive issue) In case of duplicating, Jira links all the discovered issues to the new one with the link type Duplicate
- How do you fix a bug you cant replicate? - Stack Overflow
Adding debug statements can make the problem impossible to duplicate because the debug statement itself shifts pointers far enough to avoid a SEGFAULT---also known as Heisenbugs Pointer issues are arduous to track and replicate, but debuggers can help (such as GDB and DDD)
- How to respond to a customer when their bug cant be reproduced
Do what you can to help them be confident that it should not happen again; tell them you have tried to reproduce it and have not managed to; have them stress test it; show them your documentation on the reproduction effort if you must
- How to Reproduce a Bug – Think Like a Tester
The first thing to do when you have a bug to reproduce is to gather as much information as you can about the circumstances of the issue If it’s a bug that you just noticed, think about the steps that you took before the bug appeared
- bug report - How to handle new not reproducible bug, that is known to . . .
Perhaps an alternate way to replicate the said issue would be to request the client to share his her Application User id and assuming you already have the timestamp of when the issue occurred from the screenshot shared by the client, go into the application middleware logs and identify the issue from the logs (based on shared user id and
- Fixing Issues With Jira Resolutions - Atlassian Documentation
Some Jira reports are not working or returned zero or empty report We've been able to identify 4 states a Jira Issue can be in: Resolved This would be the Correct State for issues that are considered "Resolved"; ie Done, Completed, Resolved, Closed, etc; Unresolved
- Solved: How to avoid duplicate issues being created by an . . .
You can run a JQL to identify if there are already existing records with the same Summary field as the new issue If so, cancel (or deleted if you'd like) the new issue automatically See the example below
- How do you approach an issue that youre not able to replicate?
Firstly, we could't replicate the duplicates Then we found a bug that made it possible to "create" duplicates, but it turned out that was not the root cause of the issue We pushed updates to gather more data, but we couldn't find any correlation in it No one in our team is sure of what can be causing this
- Efficient Bug Reporting and Resolution for . . . - Atlassian Community
A bug is reported in Jira, requiring more information for resolution QA team revisits the issue, uses Screenjar to record the screen or take a screenshot, and attaches it to Jira Development team uses the visual context for quicker and more accurate bug resolution
- Identify requests created on behalf of reporter | Jira | Atlassian . . .
Roles such as project Administrators and Service Desk Team members are able to create requests (issues) on behalf of other users by toggling the user in a field labeled as Raise this request on behalf of
|
|