On Mon, May 20, 2019 at 4:33 PM Ben Cotton <bcotton(a)redhat.com> wrote:
After working to implement this proposal over the summer, we have
discovered two issues with the Taiga UI that make this proposal more
annoying to community contributors than I'm willing to accept.
The first is that each custom field requires a distinct click on the
field's save button. Since the workflow makes heavy use of custom
fields, this is annoying and could result in losing data. This is
filed upstream: https://github.com/taigaio/taiga-front/issues/1029
The second is that custom fields are not available when creating
issues. You have to create the issue and then edit it to set the
custom fields. This is less bad, since most wiki-based change
proposals are edited multiple times anyway, but along with the
previous issue adds an extra level of annoyance. This is filed
Both of these issues are avoided by submitting issues via the API.
Manas (pac23), who spent this summer working on tooling for this
proposal, included this functionality in the tool. However, I don't
expect that all contributors will use the tool to submit change
proposals. The current state of the web UI is sufficient to make this
more annoying than I want the process to be.
I still like the principles behind this proposal, and if the upstream
issues are fixed (or if another suitable platform comes along), I will
revisit it. In the meantime, we'll continue using the current wiki
He / Him / His
Fedora Program Manager