Course: PES

Project group id: professor-pes

Describe the bug
En entrar al compte professor-pes abans que els projectes estiguin vinculats, el dashboard es queda penjat i no es pot ni fer logout.

To Reproduce
Steps to reproduce the behavior:

1. Anar a la pantalla inicial http://gessi-dashboard.essi.upc.edu:8888/login
2. Entra nom d'usuari i contrassenya
3. I ja estem bloquejats...

Expected behavior
En lloc de bloquejar-se, un missatge tipus "No hi ha comptes associats en aquests moments"

Screenshots

Technical context (if it is relevant):
Des del meu laptop, tant amb Firefox com en Chrome

Additional context
Avui comença la primavera

Course: PES

Project group id: PES-TEACHER

Describe the improvement
(Not related to the dashboard, but to Taiga.) Delegating onto the students the creation of additional fields to be used by the dashboard increases the likelihood of errors in the connectors, and represents an extra workload for students

Where Affects
Affects data connectors

Expected behavior
Students see in Taiga a template that they can use in order to define their user stories and tasks

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Describe the improvement
An news editor with basic capabilities like boldface, italics, itemized lists, links

Source: 2022-07-05 Reunió Setmanal

En el projecte j12c, a l'apartat mètriques, agrupat per estudiants, es veu que a l'Andrei-Constantin Popa li falten dues mètriques del GitHub: commits i modified Lines (no és que estiguin a 0, és que no hi són), però agrupat per factors sí que apareixen.
A més, mirant al Quality Model, la cosa és més rara pq veig el contrari del que m'esperaria per aquest error: a "Fullimelment of Tasks" i "Tasks Contributions" tenen associats 6 estudiants, mentre que a "commits contribution" i "modified lines" tenen associats 7 estudiants. En qualsevol cas, s'ha de revisar.

Learning Dashboard

Improvement
The server runs out of space and a solution to manage this should be seeked.

Where Affects
Problems accesing the server. For example: we can not deploy containers or access the data base bash when we have too little space.

Expected behavior
Avoid this problem as much as possible by managing the docker size. No more problems of size should arise.
It was suggested that it can be the amount of logs saved.

Course: ASW/PES

Project group id: NA

Describe the improvement
Some metrics like time effort deviation are defined for the whole team. It should be interesting to have some team metrics expressed at an individual level as well.

Where Affects
Views where the improvement should apply (take view names from URL):
3. Metrics

Course: PES

Project group id: professor-pes

Describe the improvement
Hi ha mètriques apareixen amb el pitjor valor possible (0.0) quan en realitat, la rao que valguin 0 és que no hi ha encara cap instància de l'entitat mesurada (v. exemple més a baix, mètrica de l'esquerra quan no hi ha cap tasca tancada)

Where Affects
A totes les esmentades mètriques

Expected behavior
O bé apareix el valor però sense colorejar (és a dir, que no sembli que és dolent), o bé simplement la mètrica no es mostra fins que no hi ha instàncies.

Screenshots

Technical context (if it is relevant):

Additional context

Course: ASW/PES

Project group id: Developer

Describe the bug
Metrics are not ordered by data source on Google Chrome browser, e.g. first GitHub metrics, then Taiga metrics.

To Reproduce
Steps to reproduce the behavior:

1. Open Learning Dashboard with Google Chrome
2. Go to /Metrics/CurrentChartGauge
3. Scroll down to see error

Expected behavior
Metrics are ordered by data source, as on Firefox browser.

Screenshots

Technical context (if it is relevant):

• Device: N/A
• OS: N/A
• Browser: Google Chrome
• Browser version: Version 103.0.5060.66 (Official Build)

Additional context
The Firefox browser, where the behaivor is correct, has version 102.0 (64-bit)

Course: PES

Project group id: PES-teacher

Describe the improvement
Avoid "..." in metrics' name, since it may affect readability (sometimes, it is not evident to guess the full name)

Where Affects
All cockpit-like view of metrics

Expected behavior
Visualize the entire or at least large-enough part of the metrics' name. Either by shortening the displayed name, or separating the metrics among them (probably most problematic)

Screenshots

This is an extreme example

Technical context (if it is relevant):
Non-relevant

Additional context
None

Course: PES

Project group id: PES-teacher

Describe the improvement
Reconsider the different possibilities of visualizing metrics

Where Affects
Metrics' views

Expected behavior
Currently, metrics can be visualized either without any arrangement or grouped by factors (in case of cockpits). My point is that without any arrangement, visualization is mostly useless (it is very difficult to see anything). Instead, I suggest to brainstorm more advanced capabilities. For instance, one that I see fit is to add a filter to show only team-level metrics (not individual metrics). Another view that needs some study is teacher-oriented: provide a view that facilitates the overall comparison of students (see second screenshort, a kind of mock-up).

Screenshots

This shows that the plain all-metrics view is very difficult to comprehend.

This shows an envisaged way to show metrics arranged by student (metrics also grouped by factor, which I think should be the default)

Technical context (if it is relevant):
N/A

Additional context
None

Course: PES

Project group id: PES-teacher

Describe the improvement
Implement session timeout

Where Affects
The full session

Expected behavior
The session automatically closes after let's say 15 minutes of inactivity

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Project group id: N/A

Describe the improvement
Some students forget to configure their git credentials in their local environments. Consequently, the commits that they push to GitHub from these local branches don't match with any known contributor. A simple metric showing the % of commits whose author is unknown would allow the detection of this problem.

Where Affects
Definition of a new metric and its corresponding visualizations. Perhaps it can be taken into account to define some factor that assesses the quality of commits, together with the metric that checks if the commit messages point to a Taiga task.

Course: ASW/PES

Project group id: developer

Describe the improvement
Having different categories for each factor

Where Affects
Views where the improvement should apply (take view names from URL):

1. QualityFactors/HistoricChart

Expected behavior
Add a categories creator for quality factors with different names.

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
This refactor is the same to the one done with the metrics categories

Course: PES

Project group id: PES-TEACHER

Describe the improvement
In order to allow a better contextualization of task-related metrics, having available the total number of tasks would help. Especially in the historical charts.

Where Affects
Mostly metrics, and then as needed in other views

Expected behavior
A new metric to be added in the task-related family

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW

Project group id: All

Describe the bug

• Posar els links a GitHub i Taiga al costat de les mètriques
• El botó d'informació "i" en molts casos no mostra res
• Definir els Sprints d'ASW per a tots els equips:
  • Sprint 1: de 07/10/2022 a 11/11/2022
  • Sprint 2: de 12/11/2022 a 02/12/2022
  • Sprint 3: de 03/12/2022 a 23/12/2022

Course: PES

Project group id: PES-TEACHER

Describe the improvement
Since a low/high metric/indicator value does not necessarily mean bad/good practice, I suggest to change "bad" into "low" and "good" into "high". Even if "low" really means "bad", it is more polite :)

Where Affects
All visualizations with the string "bad" or "good"

Expected behavior
New visualization updated asap

Screenshots
Not needed

Technical context (if it is relevant):
N/A

Additional context
Coming from a student's questionnaire response

Course: PES

Project group id: PES-teacher

Describe the improvement
I have thought, while evaluating the reports of the 1st iteration made by students, of an aggregated metric that would be helpful: computing the total time dedicated per student to a sprint, by summing up the number of hours of the tasks where this student appears as responsible. Of course, being aware that: a) a student has more workload that strictly the tasks in Taiga, b) a student may collaborate in a task in which s/he is not responsible. So, it would be a kind of approximation

Where Affects
As new metric, everywhere

Expected behavior
I see a new metric in the set of individual metrics, related to Task Effort

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Describe the improvement
Improve the accuracy of the metric so that large commits with third-party code are not considered and misassigned to a team member.

Possible strategies

• Filter third-party code (there is a way to do it in GitHub according to Jordi Puiguillem)
• Filter autogenerated code (as in Ruby on Rails). That means to detect and exclude the directories where such a code is stored (as suggested by Quim Motger)
• Detect big commits (from libraries, and other configurations)

Source: 2022-05-04 Reunió "Vista Professor"

Course: PES

Project group id: PES-teacher

Describe the improvement
Support all dashboard-related keywords in 3 languages (Catalan, Spanish, English) and case-insensitive. For instance: Tasca, Tarea, Task, TASK, TAsk, ...

Where Affects
Data collectors

Expected behavior
All input works for whatever language the developer uses

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

S'haurien d'arreglar els labels del factors que qualitat.

Commits management

• En el grup s11a, està a taronja però el label posa 'Well'
• En el grup s11b, està a verd però el label posa 'Down'
• En el grup s11c, també està en verd però el label posa 'Bad'.

Commits tasks Relation

• Al grup s11c en vermell posa 'Low', als altres grups posa 'Bad', s'hauria d'uniformitzar a "Low".

Deviation metrics

• Al grup j12b en verd posa 'Down', al j12c i s11a en verd posa 'Low', al grup s11b i s11c en verd posa 'Well'.

Fulfillment of tasks

• Al grup s11a, en taronja posa 'Up' en comptes de 'Neutral'

Tasks Contributions

• Al grup s11a, s11b en verd posa 'Down'
• Al grup s11c i j12b en taronja posa 'Low'. És correcte?

Task effort Information

• El grup j12b, en vermell posa 'Low'; al grup s11c, en taronja posa 'Low'; al grup j12c en vermell posa 'Bad'.

Unassigned tasks:

• Al grup j12b i s11a, en taronja posa 'Up'.
• Al grup j12c en verd posa 'Bad'.

User Stories Defintion Quality:

• Al grup s11a, en vermell posa 'Up'.

Describe the improvement
Create a website to provide more visibility to the project Learning Dashboard.

Course: ASW and PES

Project group id: all

Describe the bug
When trying to assing a certain profile the projects it has access to, no projects show up.

To Reproduce

1. Use the admin account and go to Settings.
2. Go to User Administration and click Edit on any profile.
3. Scroll down and you will see the box "Available Projects", which is empty.

Expected behavior
The box "Available Projects" should contain the existing configured projects, instead of being empty.

Screenshots

Technical context (if it is relevant):
Not relevant.

Course: PES

Project group id: PES-TEACHER

Describe the improvement
The information in historical views appears as a bunch of unstructured graphics (please see screenshot below). It would be great to allow grouping, by several factors

Where Affects
Metrics/HistoricChart

Expected behavior
I expect to be able to group-by several criteria:

• present metrics at the team level: so that I can have an overall view of the performance of the team, before I dig into the details of the individual members (I'm aware that this probably entails a subordinated issue, like defining metrics not only at member level, but also at team level)
• to be able to visualize all the detailed information of ONE member (i.e., all the metrics' values of one individual, together, probably grouped by factor, and factors grouped by indicators)
• to be able to visualize the detailed information of ONE metric (i.e., all the metric's values of all individual)

Screenshots

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Project group id: all

Describe the bug
When turning on (only turning on, not when creating it) the docker qrconnect_github container of any team, the task fails. It only works if the container is removed and recomposed.

To Reproduce
Steps to reproduce the behavior:

1. Go to Learning Dashboard folder.
2. Make sure Kafka and Zookeeper are turned on and have been for at least 2 minutes.
3. Make sure the GitHub container of the team exists and is turned off. If not, create it and turn it off.
4. Turn on the container.
5. Check the logs.

Expected behavior
It is expected to establish a successful connection and to be able to check on the logs how the polling is being made.

Screenshots

Technical context (if it is relevant):
Not relevant

Course: PES

Project group id: PES-TEACHER

Describe the improvement
When the system automatically logs off, if the user tries to execute any command, gets an error (see screenshot below). It would be better to gently offer the login screen

Where Affects
In every view, when the session is inactive for much time

Expected behavior
Present to the user the login window under session timeout situation

Screenshots

Technical context (if it is relevant):
N/A

Additional context
N/A

Equips per als quals les credencials (password) sembla que no siguin correctes i no es poden loguejar:

• s11b
• j12a (en aquest cas, potser perquè l'equip en sí encara no està disponible al dashboard)
• asw13a

Course: ASW/PES

Project group id: developer

Describe the improvement
A text that shows a description of the metrics inside each factor.

Where Affects
Views where the improvement should apply (take view names from URL):

1. QualityFactors/HistoricChart(maybe)
2. Metrics/CurrentTable

Expected behavior
Next to each factor title there is an image with a "?" or "i" symbol that when hovering over it shows the description of the metrics inside the factor.

Screenshots
Not yet

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW and PES

Project group id: all

Describe the bug
When accessing the metrics that compose a factor, through the sceen "Detailed Factors", no metrics appear.

To Reproduce

1. Select a project.
2. Go to the "Factors" screen.
3. Press on the name of any factor. You will be redirected to the "Detailed Factors" screen.
4. Press on the name of the detailed factor.

Expected behavior
Metrics should show up in the screen.

Screenshots

Technical context (if it is relevant):
Not relevant.

Additional context
This happens because an API call has a typo. More specifically, the call is "/api/qualityFactors/metric/currentcurrent", where the word current is duplicated.

Course: PES

Project group id: PES-TEACHER

Describe the improvement
In the historical view, when showing the reference segment interpolated from the values, the lowest value shouldn't be lower than 0 (see screenshot below with the problem)

Where Affects
Historical view

Expected behavior
Take 0 as lower value when necessary to avoid segments projecting below 0

Screenshots

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Project group id: Developer

Describe the bug
Depending on the interval selected for the historical view of the metrics, there are factors that have no data for this period, but are displayed and as a consequence other graphs are messed up.

To Reproduce
Steps to reproduce the behavior:

1. Go to /Metrics/HistoricChart view (e.g. hn11b)
2. Click on Interval (e.g. Delivirable 1)
3. Scroll down to 'Commits Management' factor
4. See error, this factor has data from another metric.

Expected behavior
The behavior must be similar to Factos or Detailed Factors Historical view, when the factor don't have data for the selected period/interval, it should not be shown.

Screenshots
Messed up data on Metrics Historical view:

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Project group id: Developer

Describe the bug
Sometimes after inactivity, when some action is done on dashboard without reload the page previously, it's produce error 500 "JWT String argument cannot be null or empty" (see screenshots). After that, it is impossible to go to a login page.

To Reproduce
Steps to reproduce the behavior:

1. Stay on any dashboard page
2. Wait for inactivity timeout (15 minutes)
3. Make any action without reloading the page
4. See error

Expected behavior
Understand the origin of error and permit to go to login page correctly.

Screenshots

Technical context (if it is relevant):
N/A

Additional context
If open dashboard on new tad or new secret tab it will work, maybe it's problem with cookies.

Course: ASW/PES

Describe the improvement
Kibana allows you to define your own views of ElasticSearch data, perhaps it might be interesting to define some as complementary to the dashboard. (as suggested by Jordi Piguillem)

Source: 2022-05-04 Reunió "Vista Professor"

Course: ASW/PES

Describe the improvement
Metrics related to the network section of GitHub, to see if the gitflow methodology is followed.

• For example number of abandoned branches (which have not been merged to develop) out of the total number of project branches.

Source: 2022-05-04 Reunió "Vista Professor"

Course: ASW/PES

Project group id: N/A

Describe the improvement
AS a teacher I WANT TO be able to click on the GitHub/Taiga link related to the metric I am observing SO THAT I can explore for myself the underlying causes for that metric.

Where Affects
The visualization of the metrics should include the corresponding link to their source (GitHub repo or Taiga project)

Expected behavior
Clicking on the link should open a new browser tab with the info from the GitHub/Taiga source

Course: PES

Project group id: PES-TEACHER

Describe the improvement
As future interesting metric, it would be great to measure the coherence of story points estimation in relation to the real effort that they take.

Where Affects
New metric, and then propagates as needed

Expected behavior
Add this metric to the estimation category. In fact, one could think of two metrics: 1) a simple one dividing total story points / sum of actual effort (in hours) of their tasks, 2) deviation to such ration

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: PES

Project group id: All groups

Describe the bug
Standard Deviation metrics aren't calculated properly.

To Reproduce
Steps to reproduce the behavior:

1. Go to Metrics/CurrentTable view
2. Search by 'sd' keyword
3. See 'Current Value' column value is 0.00 (error)

Expected behavior
These metrics must take the individual students value correctly, and apply them to calculate the standard deviation according to the statistical formula.

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Describe the improvement

• Categories without hard intervals, e.g. color fadings and without labels

Source: 2022-05-04 Reunió "Vista Professor"

Course: PES

*Project group id: p21a

Describe the bug
El literal en mètriques on el valor 1.0 és el pitjor, semblen estar al revés.

To Reproduce

1. Go to Factor for Backlog Management S.I.
2. See the error in Unassigned tasks

Expected behavior
Els literals tenen en compte la semàntica del valor 1

Screenshots

Technical context (if it is relevant):

Additional context

Course: ASW

Project group id: professor-asw

Describe the bug
HN22D does not appear in the list of available teams

To Reproduce
Steps to reproduce the behavior:

1. Go to Projects

Expected behavior
HN22D should appear in the list of available groups

Screenshots

Course: PES

Project group id: PES-TEACHER

Describe the improvement
Avoid including out-of-reach values in graphics. Showing these values hinders to understand what is the real maximum.

Where Affects
HistoricCharts

Expected behavior
Although ideally the same graphics could be kept and just the value's label removed, it may be necessary to finalize the Y-axis with a lower value, which can be considered acceptable

Screenshots

Technical context (if it is relevant):
N/A

Additional context
N/A

Hem vist un error de configuració tonto que no crec que sigui urgent però estaria bé arreglar en un moment donat. Al clickar sobre el botó que hi ha a la dreta de "Project" per seleccionar el projecte, hi ha un desplegable 'Profile', i apareix sempre com a opció el profile 'asw12a' (encara que l'usuari sigui un grup de PES). Seleccionant el profie 'asw12' no fa res, però s'hauria de treure...

Course: ASW/PES

Describe the improvement
Find, configure and deploy a logs analytics tool so that useful insights into when and how teams use the dashboard can be obtained.

Course: PES

Project group id: professor-pes

Describe the bug
El valor del literal informant que una mètrica val 0 és "Nada"

To Reproduce

1. Go to Metrics
2. Click on any metric who has a value 0.0
3. See reported issue

Expected behavior
El literal hauria d'estar en anglès, com la resta

Screenshots

Technical context (if it is relevant):

Additional context

Course: ASW/PES

Project group id: admin

Describe the improvement
AS AN admin user I WANT TO have a simple view in the Learning Dashboard to see the user-tracking logs.

Where Affects
A new view for admin users

Expected behavior
A scrollable view of the user-tracking logs

asw12b
El número de commits (i línies modificades) del periòde pel qual es mostren dades (5.nov a 14.nov) es manté constant. Anant al GitHub d'aquest equip es veu que sí que hi ha hagut nous commits.

asw13b
Una estudiant no ha posat correctament el seu username de GitHub (hauria de ser "huiwen8" i no "huiwen85"), així que al LD li posa commits = 0.

asw13c
No agafa correctament les mètriques del taiga, surten totes a 0. Mirant el Taiga sí que tenen tasques asignades i completades

Course: ASW/PES

Describe the improvement
Allow teachers to customize the dashboard so that

• it can be adapted to the way that a given team works; and
• the changes are only applied to that team.

Source: 2022-05-04 Reunió "Vista Professor"

Course: ASW

Project group id: asw13b

Describe the bug
The metrics 'Fulfillment of tasks' appear as 0, but the tasks are closed in Taiga.

Course: PES

Project group id: PES-TEACHER

Describe the improvement
When evaluating the iteration, the teacher may benefit from having a simple pdf report with the summary of the metrics so that it can be consulted without connection and easily browsing/scrolling.

Where Affects
It would be a functionality to be accessible from every possible screen

Expected behavior
Ditto.

Screenshots
N/A

Technical context (if it is relevant):
N/A

Additional context
N/A

Course: ASW/PES

Describe the improvement
To be able to compare the values with the global average

Where Affects
Views where the improvement should apply (take view names from URL):

1. Gauges

Expected behavior
For example, to add a line to the speedometer showing the global average

Source: 2022-05-04 Reunió "Vista Professor"

Course: PES

Project group id: PES-TEACHER

Describe the improvement
Both for the values of the metrics, and the historical view, having the concept of iteration in the tool would greatly help

PS: it is a kind of multi-issue (could be broken into two or three)

Where Affects
All levels

Expected behavior
I would expect the following functionalities:

1. To allow the definition of iterations: iteration id, start date, end date
2. To have an option in the menu allowing to select the temporal unit of work (TUoW): the full project or a particular iteration (even one could think of allowing arbitrary intervals, as it happens currently with the historical view)
3. When selecting one particular TUoW:
   a) Metrics' values are computed for this TUoW
   b) Historical view is set to this TUoW

TBD: scope. Meaning, if a TUoW is selected, does it apply to all functionalities or there can be different TUoWs in different places. E.g., is it worth to allow to have different TUoWs for computing the metrics and for looking at the historical view? E.g., when we have prediction, could we predict according to different TUoWs?

Screenshots
Just a vision

Technical context (if it is relevant):
N/A

Additional context
N/A