I've developed a secondary way of prioritization within the workboard for a project that is more granular than the priority field because you can drag the order of the tasks. For example (and needing more work): https://phabricator.wikimedia.org/project/board/404/ & https://phabricator.wikimedia.org/project/board/291/
I can also see a case where a tasks "high" priority within a specific effort, but that effort as a whole isn't as important, so the task won't be prioritized in workflow. I'm still noodling about what to do with those, but may end up with additional projects/tags for those larger efforts. Anne On Mon, Feb 9, 2015 at 1:24 AM, Amir E. Aharoni < [email protected]> wrote: > Hi, > > I often want to mark a task as high priority, because I believe that it's > an important feature to have in a project, but at the same time I know that > I cannot actually do it immediately, because I have several other important > features and I can only choose one to do now. > > Our current practice for this is to mark "High" priority, and to add a > sprint tag for the time when we plan to actually work on it. This is not > bad, but I feel that there might be a better idea. What do other teams do? > > -- > Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי > http://aharoni.wordpress.com > “We're living in pieces, > I want to live in peace.” – T. Moore > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices > > -- *Anne Gomez* // Product Manager, Fundraising https://wikimediafoundation.org/ *Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Donate <http://donate.wikimedia.org>. *
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
