"Steps to reproduce" is not a reasonable section for feature requests (Form 102)
Closed, ResolvedPublicFeature
Actions

Assigned To

Authored By

	Huji
	Aug 21 2021, 12:04 AM

Description

The new form for making feature requests on Phabriactor, located at https://phabricator.wikimedia.org/maniphest/task/edit/form/102/, preloads a template for the task. This template has a section as shown below:

**Steps to reproduce** (a list of clear steps to create the situation that made you report this, including full links if applicable):
* 
* 
*

This does not make sense. "Reproduce" is meaningful for things that already exist, such as bugs. Feature requests typically ask for something that does not exist.

The section should be remove or revised.

Event Timeline

Huji created this task.Aug 21 2021, 12:04 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 21 2021, 12:04 AM

It's asking for "a list of clear steps to create the situation that made you report this".
It's very likely that you did something before you came to think "I want this feature/enhancement". For example going to some website, or clicking a thing.

Aklapper renamed this task from "Steps to reproduce" is not a reasonable section for feature requests to "Steps to reproduce" is not a reasonable section for feature requests (Form 102).Aug 22 2021, 3:05 PM

I still think it does not make sense. But I'll let it go for now.

Do you have an idea for a better phrasing so people will explain their steps how they got to a certain point which made them ask for a feature?

What about:

"Why should this be implemented? (include full links to discussions of this proposal if applicable)"

@Platonides good idea, except that is essentially what the next question asks:

**Feature summary** (what you would like to be able to do):


**Steps to reproduce** (a list of clear steps to create the situation that made you report this, including full links if applicable):
* 
* 
*

**Use case(s)** (describe the actual underlying problem which you want to solve, and not only a solution):

In my humble opinion, asking for "step-by-step" description of why is also silly. Why not just drop the second question altogether and rephrase the third one? For instance:

**Use case(s)** (describe the actual underlying problem which you want to solve, and not only a solution; explain why this feature can address that need):

Thanks for all the feedback, appreciated!

I removed Steps to Reproduce and instead set:

Feature summary (what you would like to be able to do and where):
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
Benefits (why should this be implemented?):

I like this better.

"Steps to reproduce" is not a reasonable section for feature requests (Form 102)Closed, ResolvedPublicFeatureActions

Description

Event Timeline

"Steps to reproduce" is not a reasonable section for feature requests (Form 102)
Closed, ResolvedPublicFeature
Actions