Bug #2615
closedSome "Deployment started automatically" events are clickable but they show nothing when we click on them
Files
Updated by Nicolas PERRON about 12 years ago
- Target version changed from 2.4.0~beta1 to 2.4.0~beta2
Its bugfix will be in the next version
Updated by Jonathan CLARKE about 12 years ago
- Assignee changed from François ARMAND to Jean VILVER
Jean, can you please elaborate on this problem?
This bug report is incomplete, and is not understandable by anyone other than you without more details... Can you add in a description of the problem, copies of error messages, a screenshot of it failing, or something similar, to help other developers understand what is happening here?
Thanks!
Updated by Jean VILVER about 12 years ago
- File deployment_started_automatically_problem.png deployment_started_automatically_problem.png added
On the screenshot, we can see that after a click on the #1333 event log, unstead of showing more information on the event, it just draw a second line under the current line (that's why the line seems bold, in fact there are 2 lines).
Updated by Jean VILVER about 12 years ago
- Subject changed from Parsing problem in template "Deployment started automatically" in Event Logs to Some "Deployment started automatically" events are clickable but they show nothing when we click on them
Updated by Nicolas PERRON about 12 years ago
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
Updated by Jean VILVER about 12 years ago
- File auto_deploy_full.png auto_deploy_full.png added
- Status changed from New to Discussion
- Assignee changed from Jean VILVER to Nicolas CHARLES
With be250e549d68ea38725603d84c44b42a7a3fc14f. We have the following result:
Is the xml data is really relevant for that kind of event? (We don't always have data for this event)
Updated by Jonathan CLARKE about 12 years ago
- Assignee changed from Nicolas CHARLES to Jean VILVER
Jean VILVER wrote:
With be250e549d68ea38725603d84c44b42a7a3fc14f. We have the following result:
Is the xml data is really relevant for that kind of event? (We don't always have data for this event)
No, it isn't really for now, but it may become so in the future (for example with information about what change caused this automatic deploy). For now it's good to leave it.
Updated by Jean VILVER about 12 years ago
- Assignee changed from Jean VILVER to Jonathan CLARKE
Should we display a message explaining the xml data?
Updated by Jonathan CLARKE about 12 years ago
- Assignee changed from Jonathan CLARKE to Jean VILVER
Jean VILVER wrote:
Should we display a message explaining the xml data?
Not for now, since as you pointed out there's nothing really in there to explain...
Updated by Jean VILVER about 12 years ago
- Status changed from Discussion to Pending technical review
Jonathan CLARKE wrote:
Jean VILVER wrote:
Should we display a message explaining the xml data?
Not for now, since as you pointed out there's nothing really in there to explain...
All right. I'm changing this ticket to Technical Review.
Updated by Nicolas CHARLES about 12 years ago
- Status changed from Pending technical review to Released
- % Done changed from 0 to 100
This looks valid, thank you Jean