Vote #77358
未完了"Add" button behavior on issue page for Subtasks and Relation is inconsistent
0%
説明
In case of Subtasks, the "Add" button leads to new issue form, so it creates new issue.
In case of Related issues, the "Add" button shows small form to lookup for existing issue number and create relation for it.
This is sometimes confusing and makes me to explain those simple things.
I would like to propose to:
change the Subtasks "Add" button to "New issue", which is, to use label_issue_new in here:¶
# Returns a link for adding a new subtask to the given issue
def link_to_new_subtask(issue)
attrs = {
:tracker_id => issue.tracker,
:parent_issue_id => issue
}
link_to(l(:button_add), new_project_issue_path(issue.project, :issue => attrs))
end
optionally, add new Subtasks "Add" button opening the same small form to lookup for existing issue number and make it a subtask.¶
journals
> I would like to propose to:
> # change the Subtasks "Add" button to "New issue", which is, to use <code>label_issue_new</code> in here:
+1.
But I think "New subtask" is clearer than "New issue".
--------------------------------------------------------------------------------
Go MAEDA wrote:
> But I think "New subtask" is clearer than "New issue".
That would be fine too.
--------------------------------------------------------------------------------
I wrote a patch to change the label: attachment:22491.diff
!22491.png!
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
I would suggest to put "New subtask" into the new "+" menu dropdown:
!/attachments/download/16196/menu_item.png!
Of course, this would require that the menu items are context dependend, since it makes no sense when the user sees e.g. the Roadmap page and gets a "New subtask" entry (sub task of what?). But it does make sense when the user sees a ticket! So the menu entry could be only visible if the user has entered the ticket view.
With this the "Add" link/button could be left as it is, but with the proper meaning that the user just adds an existing ticket as subtask. It would than have the logic as the _Related issues_ "Add" link/button.
Should I create a new feature ticket for this suggestion?
--------------------------------------------------------------------------------
Robert Schneider wrote:
> Should I create a new feature ticket for this suggestion?
Yes, could you please create a new issue? We are going to change the text from "Add" to "New subtask" on this issue. Your suggestion is much bigger than what we have been discussing, so it would be better to create another issue.
--------------------------------------------------------------------------------
Here it is: #23143
--------------------------------------------------------------------------------
We'll change the label when we sill support both ways of adding a subtasks. For now I think it's not needed and will take time to be updated in all translations.
--------------------------------------------------------------------------------