Page MenuHomePhabricator

Custom task form for Wikipedia-Android-App-Backlog
Closed, DeclinedPublicRequest

Description

Please create a custom task submission form for Wikipedia-Android-App-Backlog .

Fields

I'd like default values adjusted for the following fields:

Description:

**Steps to reproduce**


**Expected results**


**Actual results**


**Screen shots**


**Environments observed**
//App version// :
//Android version// :
//Device vendor// :
//Device model// :

Tags

Should contain Wikipedia-Android-App-Backlog

Story Points:

Please hide this field

Security:

Please hide this field

Visibility

I'd like this form to be visible to all members of Phabricator. It's just a bug reporting custom form and bug reporters need not be project members!

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Have those bullet points been explicitly agreed on with the Wikipedia-Android-App-Backlog maintainers? Which items are optional?

Have those bullet points been explicitly agreed on with the Wikipedia-Android-App-Backlog maintainers? Which items are optional?

I haven't yet discussed this with them. This was my own request. This is the pattern in which most of the phab tasks are. Let me ping them to see what they have to tell. @Dbrant @Mholloway

When viewing the Wikipedia-Android-App-Backlog board, there is an item called "Report Bug" in the left sidebar, which pre-populates a task with these values. Is this any different from that?

Is this any different from that?

Technically speaking it is, as that item passes URL parameters while Kaartic proposed a custom form. Outcome might be the same though :)
The requested info is also documented on mw (should be in sync?) and for the records, previous discussion took place in T91538 and T92708...

When viewing the Wikipedia-Android-App-Backlog board, there is an item called "Report Bug" in the left sidebar, which pre-populates a task with these values.

Hmm. Haven't noted that before.

Technically speaking it is, as that item passes URL parameters while Kaartic proposed a custom form. Outcome might be the same though :)

In which case, you may close this in case if this seems redundant to that 'Report Bug' option OR You could create the proposed form and make that 'Report Bug' option open the custom form thus exploiting phabricator's feature a little.

The requested info is also documented on mw (should be in sync?) and for the records, previous discussion took place in T91538 and T92708...

Seems I'm not the first one asking this. ;-)

If the outcome is the same, then I would say we don't need a custom form.

Declining as per last comment

greg subscribed.

(Please do not add tasks directly to our kanban board; we'll take care of that when appropriate. Use our general Release-Engineering-Team project to get our attention.)

(ah, I see, you assigned to mmodel from the beginning, that's cool if he knows it's coming)

(Please do not add tasks directly to our kanban board; we'll take care of that when appropriate. Use our general Release-Engineering-Team project to get our attention.)

(ah, I see, you assigned to mmodel from the beginning, that's cool if he knows it's coming)

I'm not sure what I did wrong. I used the following to request a custom form as stated there,

https://phabricator.wikimedia.org/maniphest/task/edit/form/17/

Nothing apparently! Apparently that form assigns the task to mukunda by default. That surprised me obviously :) No worries/no fault on you!

@greg: that form assigns it to me because I'm the only person who is familiar enough with the forms and also has enough privileges to build them. It might be worth teaching someone else just to reduce the buss factor?