Members of the org are using Phab for track many types of tasks - some that I have seen are: Features, Bugs, Stories, Goals, and Epics.
Moreover we will track multiple types of tasks within the same project (Feature/Bug/Epic comes to mind).
It would be good if we had a field to support these different task types.
Having task types would allow us to:
- Represent types differently on project boards (think different colors, different sizes, styling)
- Filter for a specific type of task in search (I am just looking for bugs)
- Support different fields for different task types (Bugs have a field for "Steps to Reproduce", but features do not. Features have "story points", goals do not)
A good concrete example of this request is JIRA issues:
https://confluence.atlassian.com/display/JIRA/What+is+an+Issue
This may be a prerequisite for T92708 which aims to support specific fields for bug reporting.
----
Status quo as of 2016-05-27
| tag | task / creator | note
| ---- | ---- | ----
| #epic | {T78343} |
| #story | created by @Lydia_Pintscher |
| #category | {T119459} | used to be `#milestone` change discussed in {T129684}; milestones available now as parts of projects
| #spike | {T138380} |
| #rfc | created by @Lydia_Pintscher | originally called `#rfc`, then scope was decreased
| #tracking | imported from Bugzilla | originally called `#tracking`; different meaning in agile and hence [not to be used](https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks)
| #goal | {T127007} |
| #bug-report | [[ https://phabricator.wikimedia.org/project/manage/54/ | history ]] unclear | Archived #bug-report existed only 20 days back in 2014
| `#feature-request` | | nothing relevant exists (per T109492#2026281 and T109492#2029518 #worktype-newfunctionality is not the same)
| #roadmap | {T90360} | archived
| #release | {T99143} |
| #regression | {T75894} |
| #wikimedia-production-error | {T89292}} |
| #testme | imported from Bugzilla in 2014 |