Sep 12 2019
Aug 28 2019
Aug 27 2019
Jun 19 2019
the (Show Details) would be a great first step for us - and cover our needs. Much like the logs for Herald Rules and other areas.
There are a few pieces here, since we have to thread the needle through many layers to get where we want to go.
Apr 2 2019
Mar 31 2019
Since this is at least a little bit of actual work, I'm just going to punt until we see an actual user request.
Mar 29 2019
Feb 1 2019
These have existed for a while and recently got support for customizing sub-object behaviors in 2018 Week 50 (Mid December) and are being extended to Projects in 2019 Week 5, so it looks like they're here to stay.
Dec 22 2018
Dec 20 2018
Dec 19 2018
Dec 18 2018
@amckinley, for general context on where I'm headed here:
Sep 13 2018
Jun 12 2018
Jun 5 2018
Feb 11 2018
Jul 9 2017
Jun 14 2017
It would be really nice to default newly added fields to hidden. Going through 20+ forms to hide the fields is tedious.
May 19 2017
I also can't reproduce the original report in the general case: when I type text into the "Create Task" form, click a notification to navigate away, then press "Back", my text is recovered. This is true whether Quicksand is enabled or not.
That wouldn't actually address the original problem here (accidentally setting your computer on fire and losing work) but would address the issue in T12731.
A possible attack on this is via whatever future abuse system we ultimately might build (T10215).
May 15 2017
Apr 26 2017
Changing the type is going to run into the issue of what to do about the fields which differ between the two types. Fields which are present in the old type will continue to be displayed unless you clear them when changing types.
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 19 2017
How can I change the subtype of an existing task? This only allows me to load tasks into a form specific to their existing subtype. (i.e. I have an animal, I want to edit it and change it into a plant.)
Apr 3 2017
It was a little unclear in the walkthrough you gave on how to use it. Are the field types (animal.type plant.habitat) suppose to be hidden by default on when using a specific subtype (animal.type on plant subtype)?