Project

General

Profile

Actions

Bug #4367

closed

When creating a Group or a Rule, the category should be set to the currently selected category

Bug #4367: When creating a Group or a Rule, the category should be set to the currently selected category

Added by Jonathan CLARKE over 12 years ago. Updated over 11 years ago.

Status:
Released
Priority:
4
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When you click on "Create a new item" in the group screen, a popup appears with one item that is "Parent category". This is always set to "Root...".

This is rather annoying when you're trying to create several new groups in one category.

I would like it so that when you click "Create a new item", that popup has the "Parent category" set to either:
  • The currently selected category (if applicable)
  • Otherwise, the parent category of the currently selected group

Updated by Vincent MEMBRÉ over 12 years ago Actions #1

  • Target version changed from 2.10.0~beta1 to 2.10.0

Updated by Vincent MEMBRÉ over 12 years ago Actions #2

  • Target version changed from 2.10.0 to 2.11.0~beta1

Updated by Jonathan CLARKE about 12 years ago Actions #3

  • Target version changed from 2.11.0~beta1 to 140

Updated by Matthieu CERDA over 11 years ago Actions #4

  • Target version changed from 140 to 3.0.0~beta1

Updated by Jonathan CLARKE over 11 years ago Actions #5

  • Tracker changed from User story to Bug

Updated by Jonathan CLARKE over 11 years ago Actions #6

  • Target version changed from 3.0.0~beta1 to 3.0.0~beta2

Updated by Jonathan CLARKE over 11 years ago Actions #7

  • Subject changed from When creating a group, the category should be set to the currently selected category to When creating a Group or a Rule, the category should be set to the currently selected category

Same applies for Rules.

Updated by Nicolas CHARLES over 11 years ago Actions #8

  • Assignee set to Nicolas CHARLES
  • Target version changed from 3.0.0~beta2 to 2.10.8

This happens in 2.10

Updated by Nicolas CHARLES over 11 years ago Actions #9

  • Status changed from 8 to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/686

Updated by Nicolas CHARLES over 11 years ago Actions #10

  • Status changed from Pending technical review to 8

wait, i forgot something there

Updated by Nicolas CHARLES over 11 years ago Actions #11

  • Status changed from 8 to Pending technical review

that's ok now, i simply forgot a file where change was too small to notice :)

Updated by Nicolas CHARLES over 11 years ago Actions #12

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Updated by Vincent MEMBRÉ over 11 years ago Actions #14

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.8 and 2.11.5, which were released today (16/12/14)

Actions

Also available in: PDF Atom