Project

General

Profile

Actions
Copy link

Bug #2615

closed

Some "Deployment started automatically" events are clickable but they show nothing when we click on them

Added by Jean VILVER over 12 years ago. Updated over 12 years ago.

Status:
Released
Priority:
N/A
Assignee:
Jean VILVER
Category:
Web - Maintenance
Target version:
2.4.0~beta3
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Files

Download all files
deployment_started_automatically_problem.png (36.3 KB) deployment_started_automatically_problem.png Jean VILVER, 2012-07-06 11:39
auto_deploy_full.png (6.79 KB) auto_deploy_full.png Jean VILVER, 2012-07-19 17:40
Actions
Copy link
 #1

Updated by Nicolas PERRON over 12 years ago

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

Its bugfix will be in the next version

Actions
Copy link
 #2

Updated by Jonathan CLARKE over 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!

Actions
Copy link
 #3

Updated by Jean VILVER over 12 years ago

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

Actions
Copy link
 #4

Updated by Jean VILVER over 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
Actions
Copy link
 #5

Updated by Nicolas PERRON over 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.

Actions
Copy link
 #6

Updated by Jean VILVER over 12 years ago

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)

Actions
Copy link
 #7

Updated by Jonathan CLARKE over 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.

Actions
Copy link
 #8

Updated by Jean VILVER over 12 years ago

  • Assignee changed from Jean VILVER to Jonathan CLARKE

Should we display a message explaining the xml data?

Actions
Copy link
 #9

Updated by Jonathan CLARKE over 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...

Actions
Copy link
 #10

Updated by Jean VILVER over 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.

Actions
Copy link
 #11

Updated by Nicolas CHARLES over 12 years ago

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

This looks valid, thank you Jean

Actions
Copy link

Also available in: Atom PDF