Feature #22491

"Add" button behavior on issue page for Subtasks and Relation is inconsistent

Added by Sebastian Paluch over 1 year ago. Updated 7 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:UI
Target version:-
Resolution:

Description

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:
  1. 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
    
  2. optionally, add new Subtasks "Add" button opening the same small form to lookup for existing issue number and make it a subtask.

22491.diff Magnifier - patch (955 Bytes) Go MAEDA, 2016-04-30 08:37

22491.png - screenshot (18.4 KB) Go MAEDA, 2016-04-30 08:38

History

#1 Updated by Go MAEDA over 1 year ago

I would like to propose to:
  1. change the Subtasks "Add" button to "New issue", which is, to use label_issue_new in here:

+1.
But I think "New subtask" is clearer than "New issue".

#2 Updated by Sebastian Paluch over 1 year ago

Go MAEDA wrote:

But I think "New subtask" is clearer than "New issue".

That would be fine too.

#3 Updated by Go MAEDA over 1 year ago

  • File 22491.diffMagnifier added
  • File 22491.png added
  • Target version set to Candidate for next major release

I wrote a patch to change the label: 22491.diff

screenshot

#4 Updated by Go MAEDA over 1 year ago

  • Target version changed from Candidate for next major release to 3.4.0

#5 Updated by Toshi MARUYAMA over 1 year ago

  • Description updated (diff)

#6 Updated by Robert Schneider over 1 year ago

I would suggest to put "New subtask" into the new "+" menu dropdown:

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?

#7 Updated by Go MAEDA over 1 year ago

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.

#8 Updated by Robert Schneider over 1 year ago

Here it is: #23143

#9 Updated by Jean-Philippe Lang 7 months ago

  • Target version deleted (3.4.0)

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.

Also available in: Atom PDF