Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #10821 Sprint burndown chart 'unable to render' state
    Actions
    Infos
    #10821
    Anton KULIK (d00AK)
    2017-11-20 08:58
    2017-11-16 10:26
    11051
    Details
    Sprint burndown chart 'unable to render' state
    The burndown chart stopped rendering somewhere between 2017.10.16-2017.11.13.
    I've been away and to using Tuleap planning in this period, however frequently performing updates on server. Two days ago I added cards to the current sprint 2017.11.13-2017.11.27 and burndown shows only the dashed diagonal line triggered by "capacity", but not showing the green dots and chart line.

    Note: the tracker field names that worked previously for char rendering have not been changed, and are as following: "remaining_effort", "duration", "capacity"

    Please let me know if Tuleap team changed the above mentioned tracker field names needed for the sprint burndown to render.
    Agile Dashboard
    9.14
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2017-11-20
    Attachments
    By Anton KULIK (d00AK)
    (46 kB)
    agile-dashboard_reference_2017-11-16.png
    agile dashboard
    By Anton KULIK (d00AK)
    (57 kB)
    start-date_reference_2017-11-16.png
    start date
    By Anton KULIK (d00AK)
    (56 kB)
    duration_reference_2017-11-16.png
    duration
    By Anton KULIK (d00AK)
    (66 kB)
    remaining-effort_reference_2017-11-16.png
    remaining effort
    By Anton KULIK (d00AK)
    (173 kB)
    terminal_reference_2017-11-16.jpg
    terminal log folder
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Anton KULIK (d00AK)2017-11-17 21:51
    Ok,
    after performing the homework:
    http://tuleap-documentation.readthedocs.io/en/latest/deployment-guide/intro.html#tuleap-9-14
    on PHP 5.6 / nginx, MySQL authentication and Mediawiki configuration,

    the burndown works again, and tuleap loads much faster on nginx only. The debug mode in /etc/tuleap/conf/local.inc shows no errors

    The burndown problem might have been caused by MySQL authentication problems (I saw a lot of errors in terminal)

    I consider this bug as "resolved locally".

    Many thanks for the hints Marie!
    User avatar
    Marie Ange Garnier (marieange)2017-11-16 11:50
    Hello,

    When you access to your burndown do you always read it from agiledashboard, like shown in your screenshot?
    If yes, I think that might explain the issue: burndown values are now stored in a cache, and if something is
    wrong in cache, at first access burndown cache is generate again.
    This event is never launched in agiledashboard, that might explain why your burndown sprint are empty.

    If you connect as administrator, do you have any system_event named 'BURNDOWN_DAILY' and is event done without error?

    For your question about "debug" mode, you just have to change the level of your sys_logger_level
    in /etc/tuleap/conf/local.inc
    User avatar
    Anton KULIK (d00AK)2017-11-16 11:30
    Hello,
    I've made screenshots of tracker fields and terminal window.
    However, the switching on 'debug' mode didn't work as described in here:
    https://tuleap.net/doc/en/developer-guide/debug.html

    Please advise on how to "debug" mode.
    User avatar
    Marie Ange Garnier (marieange)2017-11-16 10:35
    Hello,

    Your tracker configuration seems alright.
    Can you activate the debug mode, then try to generate cache for burndown (Force cache generation button)
    and attach us the corresponding logs? (burndown_syslog).
    Can you please also provide me a screenshot of your burndown,
    and screenshots of your sprint for your field values :
    - remaining effort
    - start_date
    - duration

    Best regards
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Anton KULIK (d00AK)2017-11-16 10:30
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes