|
Mar. 9th, 2017|03:19 pm |
No, no, no it's not a bug. The source of the issue is not yet confirmed, we will create an investigation ticket that we will put in our backlog and will review in next sprint planning. Based on our capacity. On investigation results we will see what will be our next actions... :D |
|