-
Improvement
-
Resolution: Unresolved
-
Major
-
None
Why "useDescrIn[Value|Dot][Tooltip|Label]"?
- I was not sure about the right terms ("Value" vs. "Dot"; "Tooltip" vs. "Label"), it should be just one option, e.g.: "useDescrInValueTooltip"
Why this issue?
- Normal/default/useDescr = false:
- useDescr = true:
By default build descriptions are "only" shown as tooltips for x-axis labels, i.e. they might be skipped, because not for every build there will be an x-axis label (I think it depends on the number of builds shown).
When using useDescr = true the x-axis labels are also using the build descriptions which often does not make a lot of sense (cf. truncation of "Long description..." on the right hand side of the second image).
=> I therefore think it would be ideal to have x-axis labels like now/default (e.g. "#26 (Jan24)") and by enabling this optional new flag the tooltip for values/dots in the graph to include the build description: e.g. "Build #26 (Jan 24): First point: 6.131" (please note that the build description is just "First point")
Frankly I would not even mind loosing the old/previous "useDescr" flag 
Although/but this would not be backwards compatible...
- is related to
-
JENKINS-48887 Plot plugin ignores useDescr, keepRecords, exclZero and logarithmic when using pipeline
-
- Resolved
-
-
JENKINS-851 plot plugin should allow optional label text
-
- Open
-
[JENKINS-49158] Add plot plugin option "useDescrIn[Value|Dot][Tooltip|Label]"
Reinhold Füreder
created issue -
Reinhold Füreder
made changes -
| Link | New: This issue is related to JENKINS-851 [ JENKINS-851 ] |
Reinhold Füreder
made changes -
| Link |
New:
This issue is related to |
Reinhold Füreder
made changes -
| Description |
Original:
Why "useDescrIn[Value|Dot][Tooltip|Label]"? * I was not sure about the right terms ("Value" vs. "Dot"; "Tooltip" vs. "Label"), it should be just one option, e.g.: "useDescrInValueTooltip" Why this issue? * Normal/default/{{useDescr = false}}: !image-2018-01-25-09-55-00-841.png|thumbnail! * {{useDescr = true}}: !image-2018-01-25-09-56-30-669.png|thumbnail! By default build descriptions are "only" shown as tooltips for x-axis labels, i.e. they might be skipped, because not for every build there will be an x-axis label (I think it depends on the number of builds shown). When using {{useDescr = true}} the x-axis labels are also using the build descriptions which often does not make a lot of sense (cf. truncation of "Long description..." on the right hand side of the second image). => I therefore think it would be ideal to have x-axis labels like now/default (e.g. "#26 (Jan24)") and by enabling this optional new flag the tooltip for values/dots in the graph to include the build description: e.g. "Build #26 (Jan 24): First point: 6.131" (please note that the build description is just "First point") Frankly I would not even mind loosing the old/previous "useDescr" flag ;-) Although/but this would not be backwards compatible... |
New:
Why "useDescrIn[Value|Dot][Tooltip|Label]"? * I was not sure about the right terms ("Value" vs. "Dot"; "Tooltip" vs. "Label"), it should be just one option, e.g.: "useDescrInValueTooltip" Why this issue? * Normal/default/{{useDescr = false}}: !image-2018-01-25-09-55-00-841.png! * {{useDescr = true}}: !image-2018-01-25-09-56-30-669.png! By default build descriptions are "only" shown as tooltips for x-axis labels, i.e. they might be skipped, because not for every build there will be an x-axis label (I think it depends on the number of builds shown). When using {{useDescr = true}} the x-axis labels are also using the build descriptions which often does not make a lot of sense (cf. truncation of "Long description..." on the right hand side of the second image). => I therefore think it would be ideal to have x-axis labels like now/default (e.g. "#26 (Jan24)") and by enabling this optional new flag the tooltip for values/dots in the graph to include the build description: e.g. "Build #26 (Jan 24): First point: 6.131" (please note that the build description is just "First point") Frankly I would not even mind loosing the old/previous "useDescr" flag ;-) Although/but this would not be backwards compatible... |