Awesome, thanks! Updated to latest and confirmed.

Thanks for the report! Resolved at HEAD.

Yeah, either closing other open menus or allowing menus to be stacked on top of each other.

Yeah closing anything else open seems to be what most other applications do.

Here's an example in Maniphest where menus will overlap if you open them all (up to three in this case):

Did I miss the Dungeon Master rulebook for quest value assignment?

I mean, far be it from me to declare myself Lord King Questmaster of the Realm, that just seems like a lot and/or not a lot of valuable and desirable Quest Points for this particular task.

Is this REALLY worth 12 quest points!?

Actually on a real phone it's fine. I guess just something else is causing it at small breakpoints.

(Also I assigned this some quest points, but I guess those don't generate transactions yet).

The rest of this will roll up into other tasks which actually use it, etc.

In T10288#157504, @epriestley wrote:

If we're requiring setup and active management before we show a bar, maybe this bar is better?

(-----X~~~Y          )

The left side of the bar is "Start Date". The right side of the bar is "End Date".

... snip ...

@chad Yes, I ran across it recently. However, it's not clear to me, whether Phragile offers more comprehensive Agile functionality than the Sprint extension, or it is just a repackaged original extension with a more independent installation.

@epriestley I think you're slightly exaggerating the complexity of my suggestion. Anyway, this is my first acquaintance with reporting/charting functionality in Phabricator, so I will take time to read more about it (via the task you've linked and beyond). Since you're online, could you give me a pointer to info (beyond Harbormaster documentation), perhaps an article, which describes an end-to-end process of building a CI implementation without external CI servers, such as Jenkins (of course, if it's possible at the present time)?

They maintain a separate plugin I think for charts I think, Phragile? https://blog.wikimedia.org/2015/12/08/why-we-developed-phragile/

@chad Yes, that was my implied suggestion. Thank you for clarification. Perhaps, I need to take another look at the Wikimedia's Sprint extension (I'm trying to minimize dependencies on external Phabricator add-ons).

Maybe I misunderstand the request. It sounded like you want each project to define what a "story" is, meaning any task that lives in multiple projects, would have to implement and track each individual projects "story system", thus making task management significantly more complex (hundreds of fields to manage in each task). We don't have per project based custom fields for similar reasoning, mostly that tasks are "free range" objects on a graph, and projects just are metadata about them, not the other way around.

You're basically just asking for a magic chart feature that does whatever you want. We, bound by earthly constraints, can not build that, and the request itself is not specific enough to be helpful in defining product direction. See also T4171.

@chad I don't see how this fact affects my suggestions. When calculating progress indicators, this simply means that those indicators should reflect corresponding projections (which tasks belong to which projects).

Projects in Phabricator are just tags, and Tasks can belong to multiple Projects.

I think that there should be a single progress bar per project (sub-project), where what metrics (story points, days, ...) are used to produce the corresponding chart should be user/admin-configurable on an individual project (sub-project) basis. That way, both single-metric and more comprehensive multi-metric charts are possible, based on projects' specifics and users' preferences.

I haven't fully decided yet.

In which case I might show one bar, but color it differently if you're ahead of or behind the projects burndown rate. I don't know, I'd have to research it a little. Were you expecting to put Completion Date as a field on Milestones?

Adding a target date to a Milestone opens up other options for UI, like a mini burndown chart.

(Maybe the hybrid bar would be useful in some far-future PM-manager-manager view or whatever.)

If we're requiring setup and active management before we show a bar, maybe this bar is better?

Yeah, it doesn't convey anything otherwise, like you note.

Ah, so you wouldn't even show this bar until we implement points?

I always expected it to be directly tied to "story points" or whatever someone defines that field to be (hours, points, whatever). And that by default, there is no points in Maniphest unless someone has configured it specifically (or basically no [n] at the top of column). Even then, only on Milestones. This is why I think the number and the noun are important in defining what the bar means. Then the bar itself is just UI polish to the number data.

As a general philosophical question, what actionable information are we trying to convey with this element? I think it looks good and is probably worth adding even if it's just a "pretty bauble", and it's nice because it can show something reasonable and immediately comprehensible without any additional configuration/setup, but we're starting to descend the slippery slope of charts and graphs and I'd really like to be armed with strong product rationale as we proceed.

I'm also 90% sure I'm going to have to build a PHUIX / pure javascript version of this anyway, so the pretty photoshop pixels are probably more important than the specific markup.

Minor, but it would be nice support multiple color segments, e.g.:

Lorem Ispum Testum Thisum Tagums. Differential Public & Media Relations Design

See T5403 into T7858. I don't think this makes sense after T4100 with "Browse" UIs. All requests for this are "distinguish between multiple similarly-named projects", which is better done via "Browse".

I may have wanted to say "set loose"... :)

Can I set looks an intern on this?

Right - I've miss-read the title.

Although timeline is now linked, I think feed still isn't linked?

Now that I have a sub-par computing experience at home, some things should naturally get better.

Way better on my monitor now, thanks!

I bought an Acer XB280HK.

Here's a super helpful photo of my screen :3 :3 :3 :3

My new "gaming" PC monitor is matte and it's amazing to me how bad the color is. And it's a top of the line display. It does open my eyes a bit on some of our more subtle colors. I can see a {lightbluebackground} at the top of a web page, but not the bottom.

Yeah, I'm using a Dell U3011.

Do you have a matte screen?

Complete outlier device but; tablets with active styli (pretty much just the galaxy note range I think) use hover and it works really well.

Happy to help with conversions if that's how this gets solved.

Actually I guess (2) already got pretty much fixed in D11340.

There are broadly two issues here:

Yeah. Sorry, was using version prior mentioned diff. Thanks!

I suspect this has never worked and it isn't trivial to fix. D14168 is just some nearby code cleanup that I did while I was looking at it.

I ideally want to resolve T8588 before pursuing this since it's the more fundamental performance issue, even though this isn't particularly entwined with that.

We should do this everywhere, but if we can also improve Timeline or Hovercards, we'd like to know that too.

Thanks @chad for reminding me about feature request, will try to follow the instructions more closely.