User Details
- User Since
- Apr 21 2017, 8:42 AM (400 w, 1 d)
- Availability
- Available
Jun 6 2020
Will this feature come to diffusion for audit workflows?
Sep 14 2017
Aug 7 2017
Jul 24 2017
Jul 21 2017
May 22 2017
An optional hint for the default subtype (reasoning here) would still be appreciated.
It does indeed look better than the icons. And it is clear and comprehensible. ❤
May 14 2017
Yeah, these two bugs are probably connected. But the reproductions steps in my setup are surely more common 😄 When I tried to setup the main dashboard for our install, we changed the tabs a lot of times to find the right way to present the important infos for our users. This swallowing of tabs was pretty frustrating...
May 11 2017
May 7 2017
Well, that wasn't so obvious to me 😉 But now patched and happy. Still, there is one suggestion for the future if you will go for forward with this: I really don't understand why the default task has no icon and color. If an phabricator instance is using the subtype feature it just doesn't make any sense to give the default type no hint. When using subtypes the default type then is just like any other subtype... Disabling the possiblity to configure the hint of the default subtype could break consistent representation of the subtypes and perplex the user.
May 6 2017
Does it have to be exclusively icon or monogram hints? We use the new subtype feature very intense - but only with four subtypes. Icon hints would suffice and after one or two days the user would adapt and exactly know what is what. With more subtypes, a monogram could be a better choice. Just let the administrator decide between these two hint types via configuration?
Apr 24 2017
Easy changing of a subtype of an existing task would be on my wishlist too. In our worklow it happens fast, that a bug report or a task is tranformed to a story in the next sprint. To edit the subtype in some simple way would greatly help.
Apr 21 2017
You may be right, that the root problem is people putting to much content in Phriction articles. But even a need content seperation like this one
The root problem is clear: The ToC is useless in a highly hierarchical Phriction article with many nested headers.
It does include this direction (T9868), so I'm looking forward to this.