Trying to make Phabricator better every day. ʕ•ᴥ•ʔ
- User Since
- Oct 27 2011, 3:22 AM (278 w, 1 d)
Events stuff isn't on any roadmap, so it also could be years before it was modified.
I think https://secure.phabricator.com/book/phabricator/article/events/#ui-did-render-actions still works, that you can build a "Clone Task" action on the side of your Maniphest links and have it use that task as a templateID. Might be worth fiddling with locally.
Though this task also talks about Project Templates so maybe we should have two tasks.
All of your use cases fall into this task, I believe. That being "I want a new task based on x, y, or z" We want to group similar feature requests together for planning reasons, so multiple root problems can be solved by a common, thought-out framework. I can't guess what the UI would look like, or if we'd offer anything else like you're mentioning. I appreciate the detail on the original task, but in general we're not likely to be able to get more into a discussion on a task thats several years away at best.
How much time per day do you expect this feature to save you?
I merged this primarily for the "Create Similar Task" discussion above, which I think a similar enough feature.
- per comments
A lot of stuff just worked, so I'm going to re-test everything again because... it seemed too easy?
I'm ready to ship this and iterate. I miss the old colors.
Wed, Feb 22
Feel free to use a Phacility Test Instance and record your steps, thanks!
We require all bug reports provide complete reproduction steps. The main reason is so that anyone can follow and reproduce the bug in a local environment. Skipping details makes it difficult for most (or anyone but @epriestley) people to provide you with help.
Hi @rsmarples, unfortunately I don't know how to reproduce this based on your steps provided. Specifically, I do not see a "reference" link in the details of the commit. Do you know what additional steps I can take to see this bug locally?
- hide it everywhere
This diff was intended for the Phriction action of "Print Page" which does a bunch of other formatting vs. ⌘ + P
I reduced this diff down to just canUseInPanelContext changes -- along with better descriptions.
- filter out a few more useless ones
I'm not sure how to get rid of panel creation outside of Dashboards. Tab Panel workflow still needs them. I think we can get around that by re-thinking that creation workflow.
I actually would prefer that comment box to not be full width, like in Maniphest, etc. I think Differential/Audit it's inconsistently wide.
Yeah, but I still want Spaces to be "hard walls" around content. If it's just some minor dashboard permissions, it might be overkill (ie, they both need to see same tasks).
Basically we're in feature request territory, and we'll want to understand the root problem installing all these dashboards solves before deciding on what to build.
Do these dashboards contain sensitive information?
I think this is still the best way we have to let you if the dashboard visibility is over-restrictive or mis-installed. I'm not sure magically disappearing it solves anything. It might help to know more about what you are trying to do (was this on purpose, or a mistake) in order to try to better inform admins when they order dashboards like this.
What is your expectation here that we do?
Tue, Feb 21
Yeah I was planning on bisecting, but sounds like you're claiming this?
- truncate long names
- grey out user image on hovercards and profile
I could be wrong
This isn't a bug, but is confusing.
Mon, Feb 20
Sun, Feb 19
Please provide reproduction steps, we don't accept bug reports that ask us to go look at their server.