Document Phabricator's "Flag for Later" functionality
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Aklapper
	Jun 17 2015, 2:41 PM

Description

I received an email:

I would like to identify groups of tasks using multiple variables. It seems like projects/tags are one way. Are there other, less structured methods for identification? There will be times when I want to analyze tasks and bugs across multiple variables.

"Flag For Later" currently looks like the most suitable approach to the problem.

I cannot find any docs about Phabricator's "Flag For Later" in the Phabricator Help, only as a side note on Phab vs. Bugzilla.

Text proposal:

"Flag For Later" offers marking objects (like tasks or revisions) which "you want to remember to look at later". Eight flag colors are available. Flags are personal and private. Your flagged objects are listed on https://phabricator.wikimedia.org/flag/. They can be searched for by color or object type, in contrast to tokens.

Event Timeline

Aklapper created this task.Jun 17 2015, 2:41 PM

Aklapper raised the priority of this task from to Low.

Aklapper updated the task description. (Show Details)

Aklapper added projects: Phabricator, Documentation.

Aklapper added subscribers: Aklapper, • DStrine.

Restricted Application added a subscriber: scfc. · View Herald TranscriptJun 17 2015, 2:41 PM

Aklapper updated the task description. (Show Details)Jun 17 2015, 2:41 PM

Aklapper set Security to None.

"Flag for later" is interesting. However I'm interested in team specific, short lived identification. Here is a practical example:

Let's say my team is reporting that they have been burdened by waves of live issues. They come form a bunch of different sources at different times. They are preventing us from making progress on critical features. I would like to set up several identifying tags or other labels/identifiers... something for cross analysis.

Let's say I have 3 new identifiers to track the source of bugs: "System A" "System B" and "Dev tool A". These are the probable, large categories. I just need to know how much work is going into each.

Once I have these, I can attach them to specific bugs or tasks through a few sprints. After a few sprints I can report back on what is getting in our way, how often and when.

Is this something that projects/tags can solve? If so, i expect that fr-tech will be creating a handful of new tags in the coming weeks.

This might be a big enough topic to have a meeting and open discussion on.

Matthewrbowker subscribed.Jun 17 2015, 7:23 PM

In T102812#1375091, @DStrine wrote:

Is this something that projects/tags can solve?

I'd say so (and I'd recommend to use a team prefix for their names).

Documented "Flag for Later" under "Advanced": https://www.mediawiki.org/w/index.php?title=Phabricator%2FHelp&type=revision&diff=1882436&oldid=1882306

Aklapper added a project: DevRel-September-2015.Sep 15 2015, 11:53 AM

Document Phabricator's "Flag for Later" functionalityClosed, ResolvedPublicActions

Description

Event Timeline

Document Phabricator's "Flag for Later" functionality
Closed, ResolvedPublic
Actions