The well-named application that lets you "flag" stuff for later.
Jul 5 2019
Jul 4 2019
Thanks for the report. Fixed in D20642, which may or may not land today because of the holiday.
May 3 2019
Although I'm not entirely confident that 100% of objects which should implement ExtendedPolicyInterface actually do today, I think we've gotten pretty much all of them. This approach also seems stable.
Jan 26 2018
Nov 23 2017
I'm unable to close this, but I believe this to be resolved (or at least my specific repro of flags via herald no longer applies I believe).
Jul 3 2017
Mar 21 2017
Jan 9 2017
Started building and insanely easier as an application. "Favorites" unless you have a better suggestion. Seems more flexible.
Jan 6 2017
Yep, that looks good to me.
Just for my own understanding:
Jan 4 2017
I'm not actually sure which will end up being easier, I think they have like 95% of the same problems. Quick Create probably is a bit easier, though.
I'm for whichever is easiest, since the other will fall in line quickly after.
You were thinking about doing this one first, then Home later, right?
@epriestley I feel like we had this conversation on how to implement this somewhere... (on a diff)? Not sure where these extend from, just move it into Personal/Global settings?
Dec 13 2016
Aug 7 2016
Aug 5 2016
Jul 4 2016
Apr 17 2016
Apr 11 2016
Mar 15 2016
Mar 14 2016
It was a bug that it disappeared.
Ah. Looks like I just needed to upgrade as this change was made in the last month or so (I last upgraded late Feb). Didn't see this change mentioned in the changelog, or a task for it, so assumed it still wasn't possible. What you have implemented is perfect for us. Sorry for the noise.
Projects are flaggable under the manage page. We have no plans to make Workboards flaggable.
Mar 9 2016
Jan 6 2016
Flags currently has this unwieldy dropdown, which will only get worse over time as more applications and object types are added. It would be better to use a typeahead, like the one in global search:
I removed this because the implementation was pretty hacky (saved the rule as a text string, wasn't translatable).
good enough for me
@chad, not sure if you have design thoughts here, but I think this is broadly reasonable.
I think it's too hard for us to guess user intent here. There's nothing a user can do which strongly signals that their flag is obsolete, since flags mean a lot of different things (in your use case, it sounds like there's no single action you take which clears the flag, just "the next action after you added the flag"). Other users (myself included) use flags for different reasons, including as long-term bookmarks. Guessing intent is also difficult because you can flag many kinds of objects, not just tasks, and we'd strongly prefer features which can be implemented globally.