Project

General

Profile

Actions
Copy link

Bug #4367

closed

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

Added by Jonathan CLARKE almost 11 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
4
Assignee:
François ARMAND
Category:
Web - Nodes & inventories
Target version:
2.10.8
Pull Request:
https://github.com/Normation/rudder/p...
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
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.10.0~beta1 to 2.10.0
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.10.0 to 2.11.0~beta1
Actions
Copy link
 #3

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.11.0~beta1 to 140
Actions
Copy link
 #4

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions
Copy link
 #5

Updated by Jonathan CLARKE almost 10 years ago

  • Tracker changed from User story to Bug
Actions
Copy link
 #6

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 3.0.0~beta1 to 3.0.0~beta2
Actions
Copy link
 #7

Updated by Jonathan CLARKE almost 10 years ago

  • 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.

Actions
Copy link
 #8

Updated by Nicolas CHARLES almost 10 years ago

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

This happens in 2.10

Actions
Copy link
 #9

Updated by Nicolas CHARLES almost 10 years ago

  • 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
Actions
Copy link
 #10

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from Pending technical review to 8

wait, i forgot something there

Actions
Copy link
 #11

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from 8 to Pending technical review

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

Actions
Copy link
 #12

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 10 years ago

  • 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
Copy link

Also available in: Atom PDF