Team-Velocity gadget does not show all the boards and does not show correct data for the selected sprints.

Issue #28 resolved
Viktoriia Hliebova created an issue

Hello Dear Support Team,

Our user has faced some difficulties while setting up Team-Velocity gadget. Here is the original message:

When I setup the gadget, it does not show all the boards (e.g. this board is not listed in the For those that are there, instead of "last 3 sprints" it shows some random data from 2015.

Could you please advise?

Comments (8)

  1. Danut M [StonikByte] repo owner
    • edited description

    Hi Viktoriia,

    Thanks for posting.

    The gadget shows only the boards of type "Scrum"; the Kanban boards are not shown as they do not contain sprints that are required by the Team Velocity gadget. For Kanban please use the Kanban velocity gadget. So please double check what board type have the ones that are not listed.

    For verifying the correctness of the data displayed, please send to support@stonikbyte.com the following: - a screenshot with what the Velocity Gadget displays - a screenshot with its settings (if it is other than the one already attached) - a screenshot with the Velocity Chart report of Jira for the selected board that displays both the chart and data table

    Thank you, Danut Manda

  2. d_arkhipov

    Hello Danut, Please find below the three screenshots that you have requested. Indeed all the boards in question are Scrum boards. Let me know if you need any other info. Capture2.PNG Capture1.PNG Capture3.PNG

  3. Danut M [StonikByte] repo owner

    Hi Dmytro & Vicktoriia,

    Thanks for sending all this info. Indeed it appears to be something wrong.

    We would require a few more data. But if you don't mind I would like to move the discussion over the email as it might contain details that should not be publicly shared.

    So please send an email to support@stonikbyte.com on this matter and I will reply with the next steps.

    Thank you,

    Danut Manda

  4. Danut M [StonikByte] repo owner

    This issue was fixed a while ago. It was caused by some permission configurations on customer side. Also, there were some fixes in our add-on, which were included in latest versions. Closing ticket.

  5. Log in to comment