Issue Details (XML | Word | Printable)

Key: JRA-3845
Type: Task Task
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Scott Farquhar [Atlassian]
Votes: 2
Watchers: 6
Operations

If you were logged in you would be able to see more operations.
JIRA

Create 'issue tracking best practices guide'

Created: 31/May/04 07:14 PM   Updated: 11/Apr/08 01:41 PM
Component/s: Documentation
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Brendan Patterson [Atlassian], Jeff Turner [Atlassian], markus and Scott Farquhar [Atlassian]
Since last comment: 26 weeks, 1 day ago
Labels:


 Description  « Hide
From a customer:

"Procedures and policies for issue management - I was stunned not to find this. Perhaps it is there, and I've just missed it. I find no documentation on setting up an environment in which JIRA can be used effectively. Such a document should include things like "search the bug list before submitting a new one", etc. etc. All the typical procedures that all your customers will have to put into place.

Writing this stuff, and making it available (perhaps with a license: you may use this documentation if you have a license for JIRA), would make even more managers want to buy your product - it makes our lives easier. Of course, we will want to adapt the documentation, but these kinds of guidelines are pretty general and embraced by most that use this kind of product. I am a strong believer in reuse. It strikes me that all of your customers are doing something similar here. Prime refactoring material."



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] added a comment - 14/Jun/04 11:09 PM
If anyone has concrete ideas about what should be in this doc (beside "search for bugs before raising them"), please let us know here..

markus added a comment - 07/Jul/06 01:05 AM
The best practices is certainly not complicated for someone who has used a tool such as JIRA in the past. It is something very strange for people lacking any formal testing experience.

A bare-bones process could be as detailed below

  1. test scripts are created
  2. tester executes script
  3. test discovers an anomaly
  4. tester create new JIRA bug/issue; including the following information
    1. script executed
    2. expected result
    3. actual result
    4. if it is repeatable
  5. daily/weekly/monthly bug triage meeting
    1. project manager, test lead, technical lead must attend
    2. all new bugs are reviewed
    3. bugs deemed necessary to address are assigned to specific developers or tech lead
  6. developer fixes issue
  7. developer marks issue as resolved
  8. developer assigns issue to tester who created the issue
  9. tester validates that the fix from the developer is correct and closes the issue.

Brendan Patterson [Atlassian] added a comment - 11/Apr/08 01:41 PM
Has there been any progress on this? I get this question about 'JIRA best practices' all the time. It would be nice to have a kind of Wikipatterns like site for JIRA to point people at.

Also the list above is good for an initial software development process, but lots of companies want to use JIRA for other things such as customer support (like Atlassian does) and basic issue / task tracking unrelated to software development across different departments (a bit like it seems Linden Labs does).