Page MenuHomePhabricator

Incorrect tasks status in email notification
Closed, InvalidPublic

Description

I have created a custom maniphest status by adding configuration to : http://phabricator.example.com/config/edit/maniphest.statuses/

New status configuration looks like this :

"inprogress": {

  "name": "In Progress",
  "closed": false,
  "prefixes": [
    "open",
    "opens",
    "reopen",
    "reopens"
  ]
  "keywords": [
    "open"
  ]
}

However, when I changed the status of the task to "In Progress" , I get email notification with this text: " Username closed this task as "Unknown Status"."
The message in email notification is incorrect. Tasks status is "In Progress" and task itself is "Open".

EDIT: in my case : ./phd restart , fixed the issue.

Thanks for Your help!

Event Timeline

• ryzhas updated the task description. (Show Details)
• ryzhas updated the task description. (Show Details)
• ryzhas updated the task description. (Show Details)

This report is missing required information.

epriestley added a subscriber: epriestley.

I can't reproduce this either. Here's what I did:

  • Changed maniphest.statuses to define an "In Progress" status (note that the provided JSON definition is not valid, as it is missing a comma).
  • Changed a task to this status from the web UI.
  • Observed the content of the generated email.

However, the email generated correctly.

Here's the config change I made:

Screen Shot 2016-11-18 at 10.41.20 AM.png (1×2 px, 157 KB)

Here's the edit I made to a task:

Screen Shot 2016-11-18 at 10.42.56 AM.png (272×2 px, 75 KB)

Here's the body of the email this edit generated:

$ ./bin/mail show-outbound --id 34980
...
TEXT BODY
hector changed the task status from "Open" to "In Progress".
hector added a comment.


  This is now in progress.

TASK DETAIL
  http://local.phacility.com/T194
...

To move forward, we need additional information about what steps we should take to reproduce this issue in a local development environment (for help, see Providing Reproduction Steps).

We can't help without this information. If we don't receive this information in a few days, we'll close this task as invalid.

Wow, isy is quite a productive little worker!

Closing for now, happy to reopen with reproduction steps we can follow.