Actions
Bug #10515
closedCannot go back to the previous page on node details
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
43
Name check:
Fix check:
Regression:
Description
Nothing happens when we try to go back to the previous page if we are on node details.
Updated by Raphael GAUTHIER over 7 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.0 to 4.1.1
- Priority set to 0
Updated by François ARMAND over 7 years ago
- Target version changed from 4.1.1 to 4.0.4
So, the problem is that there is two "Rudder - search nodes" in the history. In 3.1, that was the case, but clicking two times on back was working. Since 4.0, clicking one time to bach trigger again the function that stack a second identical page in the back history, and so you can't go out of the loop. Well, actually, going back further in the history (righ click on back to have the list of recent places) works.
Updated by Benoît PECCATTE over 7 years ago
- User visibility changed from First impressions of Rudder to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 43
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.0.4 to 4.0.5
Updated by Raphael GAUTHIER over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1635
Updated by Jonathan CLARKE over 7 years ago
- Status changed from Pending technical review to New
- Assignee deleted (
Vincent MEMBRÉ)
Updated by Jonathan CLARKE over 7 years ago
- Status changed from New to Pending technical review
- Assignee set to Vincent MEMBRÉ
Updated by Anonymous over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6d3d6076bed83d8de3497c2de641a1cb86f3c052.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.5 and 4.1.2 which were released today.
- 4.0.5: Announce Changelog
- 4.1.2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions