Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0015052 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | minor | always | 2010-10-27 18:02 | 2022-02-01 08:09 | ||||||
| Reporter | dmitry_mezentsev | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | low | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | main | SCM revision | |||||||||
| Merge Request Status | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Support ticket | |||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0015052: Registration flow is not consistent in the application | ||||||||||
| Description | If user agrees to enable Heartbeat Registration pop-up does not appear after it - it appears on the second login. If user declines Heartbeat Registration pop-up appears. | ||||||||||
| Steps To Reproduce | You can check it in live.builds | ||||||||||
| Proposed Solution | As a minimum the flow should be consistent. We should always display Registration pop-up after Heartbeat or always only at the second login. IMHO better at the first one. As for me with this we can expect more registrations course it will look like a step in a bigger processed of setting up the system. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-10-27 18:02 | dmitry_mezentsev | New Issue | |
| 2010-10-27 18:02 | dmitry_mezentsev | Assigned To | => alostale |
| 2010-10-27 18:02 | dmitry_mezentsev | OBNetwork customer | => No |
| 2010-11-02 08:00 | alostale | Status | new => scheduled |
| 2010-11-02 08:00 | alostale | Assigned To | alostale => gorkaion |
| 2010-11-02 08:00 | alostale | fix_in_branch | => pi |
| 2011-01-18 12:45 | gorkaion | Relationship added | has duplicate 0015407 |
| 2012-09-04 16:38 | dmiguelez | Assigned To | gorkaion => alostale |
| 2015-02-24 11:17 | alostale | Triggers an Emergency Pack | => No |
| 2015-02-24 11:17 | alostale | Priority | normal => low |
| 2015-02-24 11:17 | alostale | Status | scheduled => acknowledged |
| 2015-02-24 11:17 | alostale | fix_in_branch | pi => |
| 2015-03-17 14:38 | alostale | Assigned To | alostale => platform |
| 2016-12-01 13:22 | alostale | Type | defect => design defect |
| 2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |