Page MenuHomePhabricator

Add option to feature: Option of "completed" in Status list of task.
Closed, WontfixPublic

Description

I have previously worked on GUTS (Google Unified Ticketing System v3) while my employment with Google. They had the feature of "Resolved" which did not meant that the task will be marked as "Closed" at the same time, instead they had "Resolved & Closed" as an additional option.

All the task that were marked "closed/resolved" by general user were only reactivated by the administrator or assignor.
In Phabricator I have implemented the functionality by appending settings for "Done"(self created status) in the maniphest.status.
I will appreciate if a similar feature is incorporated globally. It really helps in differentiating among the tasks that were "completed" and those that were directly closed.

Event Timeline

sameep.agarwal raised the priority of this task from to Normal.
sameep.agarwal updated the task description. (Show Details)

The maniphest.status config option allows you to specify any status as being treated as "closed".
Actually there is no single "closed" status. But resolved, invalid, spite & wontfix are all treated as closed.
Feel free to rename / change this properties to your liking and your preferred workflow.
What you describe would be somethink like:

{
  "open": {
    "name": "Open",
    "special": "default"
  },
  "resolved": {
    "name": "Resolved",
    "name.full": "Resolved",
    "closed": false,
    "prefixes": [
      "fix",
      "fixes",
      "fixed",
      "resolve",
      "resolves",
      "resolved"
    ],
    "suffixes": [
      "as resolved",
      "as fixed"
    ]
  },
  "closeresolved": {
    "name": "Resolved & Closed",
    "name.full": "Closed, Resolved",
    "closed": true,
    "special": "closed",
    "prefixes": [
      "closed",
      "closes",
      "close"
    ]
  },
  "wontfix": {
    "name": "Wontfix",
    "name.full": "Closed, Wontfix",
    "closed": true,
    "prefixes": [
      "wontfix",
      "wontfixes",
      "wontfixed"
    ],
    "suffixes": [
      "as wontfix"
    ]
  },
  "invalid": {
    "name": "Invalid",
    "name.full": "Closed, Invalid",
    "closed": true,
    "prefixes": [
      "invalidate",
      "invalidates",
      "invalidated"
    ],
    "suffixes": [
      "as invalid"
    ]
  },
  "duplicate": {
    "name": "Duplicate",
    "name.full": "Closed, Duplicate",
    "transaction.icon": "fa-times",
    "special": "duplicate",
    "closed": true
  },
  "spite": {
    "name": "Spite",
    "name.full": "Closed, Spite",
    "name.action": "Spited",
    "transaction.icon": "fa-thumbs-o-down",
    "silly": true,
    "closed": true,
    "prefixes": [
      "spite",
      "spites",
      "spited"
    ],
    "suffixes": [
      "out of spite",
      "as spite"
    ]
  }
}
chad closed this task as Wontfix.EditedJan 8 2015, 3:03 PM
chad claimed this task.
chad added a subscriber: chad.

Please see https://secure.phabricator.com/book/phabricator/article/feedback/ if you are new to Phabricator. Historically, we're not likely to add features to Phabricator simply because they existed in another product a user liked. We have a very small unpaid team (3 people) and have a very focused way of building product. We're always happy to solve real problems, so if you state your problem, there is likely already some form of a solution already filed in most cases.

(I believe @fabe covered the main part of the feature request)

Buddy, I had already been using that by tweaking the JSON file in the config,. Just wanted to know about your plans of introducing it in the application. Anyways, thanks for your help guys. I really appreciate this product and would continue to use it at our organization.

It has really helped me track the projects for the firm and users are enjoying it. Looking forward to more in future. Thanks for responding to the request.