After D20305, this can be "fixed" with this change:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 8 2019
Aug 8 2019
Aug 7 2019
Jul 31 2019
Jul 3 2019
Jul 2 2019
Jun 29 2019
Jun 18 2019
Jun 6 2019
May 30 2019
Mar 26 2019
Mar 21 2019
Mar 11 2019
To summarize the state of the world here:
Feb 28 2019
In T6409#216988, @denghaodna wrote:Would be happy to see this feature. My company use different team names as columns of the work board. When a task is reassigned from a dev to a tester, I need to manually move it from Dev column to QA column.
With this feature implemented, I would be able to configure a rule that when a task is assigned to a specific person, the task will be automatically moved to a column, say the Dev column for example.
Feb 16 2019
It sounds like real-time updates will more-or-less moot this.
Nov 29 2018
This isn't an actionable task. It covers too much ground, describes too many features, and most of it lacks compelling use cases.
No plan to continue on this?
Nov 7 2018
@epriestley we are using the "menu item" solution that you described above, and the primary remaining pain point is that when you click on a link, the menu highlights "workboard", which confuses some users, because they expect the link (i.e. the menu item they just clicked on) to be highlighted.
Nov 2 2018
Awesome, thanks @epriestley!
Nov 1 2018
Sorry! That reproduces cleanly for me too. I must have made a mistake following the reproduction steps or overlooked something. D19768 should fix this.
Oct 31 2018
I just tested and indeed @joshuaspence's steps are reproducible on https://phabricator.wikimedia.org
In T13208#242142, @epriestley wrote:To reproduce this issue, just need to Click on Default Column -> View as Query then leaving without Saving the query.
These reproduction steps don't work for me, and don't make sense given how the software works. If you believe you have a set of reproduction steps, can you walk through them step-by-step in more detail so I can reproduce the issue?
If anyone can come up with reproduction steps which actually work, this will probably take me about 3 minutes to fix. The only thing blocking this is that I have no idea how to reproduce it.
Oct 30 2018
To reproduce this issue, just need to Click on Default Column -> View as Query then leaving without Saving the query.
I just a way to fix this. After using "/query/all" to get in the board. We can click on the "All Tasks" Filter -> "Save as Default" and we don't get issue 404 anymore.
To reproduce this issue, just need to Click on Default Column -> View as Query then leaving without Saving the query.
Workaround: add "/query/all" at the end of the url also work fine.
I am still reviewing the database to to set back to the buitin query
Oct 29 2018
In T13208#242133, @20after4 wrote:@dlgiang: if you go to maniphest and choose any of the existing saved queries, you will find the ID in the resulting url.
@dlgiang: if you go to maniphest and choose any of the existing saved queries, you will find the ID in the resulting url.
Oct 26 2018
In T13208#242106, @aklapper wrote:@dlgiang: T13208#241682 above links to https://phabricator.wikimedia.org/T199207#4413718 describing a workaround
@dlgiang: T13208#241682 above links to https://phabricator.wikimedia.org/T199207#4413718 describing a workaround
Are there any workaround for this issue ?
Oct 1 2018
It seems to be a fairly recent problem so there must be some code change that started triggering it. The worst part, IMO, is that the workboard breaks in a not-entirely-obvious way instead of falling back to a default query. It took me a while to debug the issue the first time it occurred.
There should be no code anywhere in Phabricator to delete saved queries. The expectation is that they are never deleted or garbage collected because they may have been embedded in other pages, sent via email, etc., and deleting a saved query will break any use of the link in a permanent/external context. The table is expected to grow without bound, although at a slow enough rate that it does not create a maintainability issue.
In T13208#241647, @epriestley wrote:[..] the issue is actually with persisting the query in the first place, not deleting it?
Could it be that a user assigns it to one of their "personal" custom queries and then later they delete that query by way of the maniphest saved query ui?
I'm not sure what's caused this either but I've seen it twice on wikimedia's production install.
My expectation is that no upstream code exists to ever delete saved queries. My guess is that either:
Jun 5 2018
Apr 13 2018
D19366 adds a "View as Query" option to the dropdown on workboard columns. This will take you to the Maniphest query results page with a query that selects exactly what was shown in the column when you selected the item.
Mar 5 2018
Feb 25 2018
Feb 14 2018
Feb 13 2018
I don't currently plan to implement this. I think T5474, T10333, T11036, and using the Maniphest list view with "Group By" address this use case to varying degrees (if you "Group By: Task Status" and then turn your monitor sideways, you pretty much get the desired result). It's possible we'll end up back here in the future, but since I'm not planning to scope this into T13074 I'm going to close it until those changes land and further use cases arise.
Workboards have offered access to multiple task creation forms for some time.
I think D18665 seems to generally have been satisfactory here, so I'm going to call this resolved until additional use cases arise.
This task is a giant mess with pretty much no remaining actionable use cases. See T13074 for plans. If you want some use case here included in that, file a description of your problem via support pact.
I don't currently plan to do this. At a bare minimum, T5474 may moot it.
Some of this is fixed; the rest of it doesn't have outstanding customer requests.
Feb 8 2018
@kislinsk Is it possible to externalize your solution? I have no information about the status of Phabricator supporting extensions but when there is a way to separate your solution from the core cleanly, why not creating a repository on GitHub? I would love to use this right now! :D
Jan 19 2018
Dec 29 2017
I second this:
Nov 30 2017
Nov 28 2017
I don't plan to pursue this.
Sep 29 2017
Aug 21 2017
Will add this as a request for us to our planning log
Aug 6 2017
Aug 2 2017
See Planning for information on progress and priorities.
Any progress on this issue? Agreed with @dariusz that this is my number one pet peeve. This is a pretty large omission from bulk editing capabilities for a column. I can set a task to move to a different column when I am commenting in a task. I'd expect the ability to do the same bulk process on a column of tasks, even if I could only move those tasks within the same workboard. Dragging and dropping tasks individually is extremely time consuming when I have to move tasks between columns.
This is an unusually low-tech solution but I can't think of any reasons why it won't work.
I'm obviously low on AM brian power today.
Heh, that was going to be my suggestion in the original discourse post, but I figured it was too simplistic. Glad to hear we're on the same page. Thanks everyone!
That sounds much easier than all the solutions I came up with.
Is there any reason that the rule "if any menu items have the same link target as the request URI, highlight the first one" wouldn't work?
Or maybe there is a simple way to get the link to highlight, I couldn't think of one though.
A link doesn't stay highlighted if clicked on. Like dashboards, I can understand wanting multiple board views from the sidebar.
- What's the root problem?
- Why can't they use links?
- How is this different from T12374?
Jul 9 2017
Jul 7 2017
Jul 5 2017
+1 that this is needed and complements T5474.
+1 that this is really needed.
Jul 2 2017
Thanks for the reply @chad.