•  
      request #12827 Backlog list in "Sprints Planning" not loaded
    Infos
    #12827
    Thomas Konzett (thoko)
    2019-01-29 14:52
    2019-01-24 09:38
    13668
    Details
    Backlog list in "Sprints Planning" not loaded

    encounter a problem: the backlog cannot be loaded on the scrum agiledashboard -> "sprints planning" page. I'm using very latest tuleap and centos7 (all fully patched). The database was taken over from a tuleap 9, but upgrade did work flawlessly. Did try as well on a new fresh mysql database. The URL that fails (local site):
    https://somepath.domain.local/api/v1/milestones/421/backlog?limit=50&offset=0

    JS console shows:

    Possibly unhandled rejection: {"data":"","status":500,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","params":{"limit":50,"offset":0},"headers":{"Accept":"application/json, text/plain, */*"},"url":"/api/v1/milestones/421/backlog"},"statusText":"Internal Server Error","xhrStatus":"complete"}

    and nginx error spits out:

    2019/01/25 08:45:28 [error] 23256#0: *29 FastCGI sent in stderr: "PHP message: PHP Notice:  Error encountered while retrieving data ==> SELECT SQL_CALC_FOUND_ROWS linked_art.*
                    FROM tracker_artifact parent_art
                        INNER JOIN tracker_field                        f          ON (f.tracker_id = parent_art.tracker_id AND f.formElement_type = 'art_link' AND f.use_it = 1)
                        INNER JOIN tracker_changeset_value              cv         ON (cv.changeset_id = parent_art.last_changeset_id AND cv.field_id = f.id)
                        INNER JOIN tracker_changeset_value_artifactlink artlink    ON (artlink.changeset_value_id = cv.id)
                        INNER JOIN tracker_artifact                     linked_art ON (linked_art.id = artlink.artifact_id )
                        INNER JOIN tracker_artifact_priority_rank                       ON (tracker_artifact_priority_rank.artifact_id = linked_art.id)
                         -- exlude all those linked to wrong artifacts
                        LEFT JOIN (
                            tracker_artifact as su...
    PHP message: PHP Fatal error:  Uncaught TypeError: Argument 2 passed to AgileDashboard_Milestone_Backlog_DescendantItemsFinder::getItemsForUser() must implement interface Tuleap\DB\Compat\Legacy2018\LegacyDataAccessResultInterface, boolean given, called in /usr/share/tuleap/plugins/agiledashboard/include/AgileDashboard/Milestone/Backlog/DescendantItemsFinder.class.php on line 196 and defined in /usr/share/tuleap/plugins/agiledashboard/include/AgileDashboard/Milestone/Backlog/DescendantItemsFinder.class.php:216
    Stack trace:
    #0 /usr/share/tuleap/plugins/agiledashboard/include/AgileDashboard/Milestone/Backlog/DescendantItemsFinder.class.php(196): AgileDashboard_Milestone_Backlog_DescendantItemsFinder->getItemsForUser(Object(PFUser), false, '3')
    #1 /usr/share/tuleap/plugins/agiledashboard/include/AgileDashboard/Milestone/Backlog/Backlog.php(179): AgileDashboard_Milestone_Backlog_DescendantItemsFinder->getMilestoneOpenUnplannedBacklogItemsWithLimit
    
    

    The Scenario I test:

    I could reproduce as well in a fresh install (centos7 remote database):

    • create new agile scrum board (with new release and at least 1 sprint)
    • add user story in backlog
    • move story to a release
    • move story to a sprint in "sprints planning view"
    • move story back to backlog
    • refresh in "sprints planning" cannot load the backlog anymore
    Agile Dashboard
    10.9
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2019-01-29
    Attachments
    Empty
    References
    References list is empty

    Follow-ups

    User avatar
    Glad you solved your issue, I'm closing the artifact.

    best regards

    • Status changed from New to Closed
    • Close date set to 2019-01-29
    User avatar
    Thomas Konzett (thoko)2019-01-28 17:31
    I'm sorry, it really seems to be the different database system to be blamed. I restored my DB on the supported mysql (following the full installation guide) and now those flaws are gone. Thx for the great assistance.
    User avatar

    We never did any qualification with mariadb. Did you check with mysql 5.7 ( w/o STRICT_ALL_TABLES, STRICT_TRANS_TABLES or ONLY_FULL_GROUP_BY)

    User avatar
    Thomas Konzett (thoko)2019-01-25 14:02
    hmmm, mine is a mariaDB
    mysqld Ver 10.1.23-MariaDB-9+deb9u1 for debian-linux-gnu on x86_64 (Debian 9.0
    User avatar
    Thomas Konzett (thoko)2019-01-25 11:59
    • 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
    Thomas Konzett (thoko)2019-01-25 08:45
    • 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