search

jiuntian / IssueTrackerAssignment

0 stars 0 forks source link

Status of an Issue #6

Closed lohyenshen closed 3 years ago

lohyenshen commented 3 years ago

Could you kindly elaborate on when should the status of an issue be categorized into one of "Open", "In Progress", "Resolved", "Closed".

jiuntian commented 3 years ago

Let's take this example: When a ticket is opened, it will be "Open". When someone is taking the responsibility for this particular ticket, and starting his progress, it will be "in progress". When the ticket is done or completed, it will be "Resolved". If the ticket is cancelled, it is moved to "Closed". You may refer to the issue cycle figure given in the question. image

lohyenshen commented 3 years ago

May I know if the below description is correct?

creator -> "open" (open a new issue/ reopen a issue), -> "closed" (close a issue after assignee resolved it)

assignee -> "in progress" (starts working on a issue assigned) -> "resolved" (once he/she has provided solution to the issue)

jiuntian commented 3 years ago

It is not restrict to just creator to close the ticket, assignee can also close it whenever necessarily. Same goes to reopen, assignee can reopen the ticket, when he/she think that the problem still persist or did not solved.

Feel free to try some of common issue tracker system online to know more about these: Jira (free trial available)

jiuntian commented 3 years ago

What's more, you can take this Github Issue as an example as well. Both you and me can close this ticket, and reopen it.

lohyenshen commented 3 years ago

Can the creator set the status of an issue to "In Progress" & "Resolved"?

jiuntian commented 3 years ago

ideally, creator should be able to move the issue to "Resolved" as well. "In progress" would be better to be reported by the one who is working on the issue.

However, there are many different philosophy of issue lifecycle, I am just giving some suggestions only.

lohyenshen commented 3 years ago

Noted with thanks