dashboard issueshttps://gitlab.servus.at/aura/dashboard/-/issues2024-03-11T03:02:29+01:00https://gitlab.servus.at/aura/dashboard/-/issues/102[STORY] As a programme coordinator, I want to permanently delete a show, for ...2024-03-11T03:02:29+01:00David Trattnig[STORY] As a programme coordinator, I want to permanently delete a show, for undoing a created show by mistakeParent: #149+
---
The o94 legacy backend provides a "delete show" feature. This permanently deletes a show and all related data.
Similarly as the o94 backend, the delete button should asks for confirmation by outlining the consequences...Parent: #149+
---
The o94 legacy backend provides a "delete show" feature. This permanently deletes a show and all related data.
Similarly as the o94 backend, the delete button should asks for confirmation by outlining the consequences.
---
Side note: In most cases a show is deactivated, rather than deleted, in order to keep history data. Compare the [relevant documentation](https://docs.aura.radio/en/latest/user/station-administration.html#deactivating-and-deleting-users).1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/144[STORY] as a radio host, I want to see a progress bar / wheel when entering "...2023-11-09T11:29:58+01:00Margarethe Maierhofer-Lischka[STORY] as a radio host, I want to see a progress bar / wheel when entering "upload image" in the image uploader, so I can be sure that the upload of my show image is working correctly.When uploading an image to the show description / Sendereiheninfo and to the show notes, sometimes the upload can take more time depending on image size and internet connection. It would help a user to understand the upload is working co...When uploading an image to the show description / Sendereiheninfo and to the show notes, sometimes the upload can take more time depending on image size and internet connection. It would help a user to understand the upload is working correctly if an upload progress bar or wheel was displayed.https://gitlab.servus.at/aura/dashboard/-/issues/245[STORY] as ProKo, I want a confirmation dialog when using the "re-activate" b...2024-01-17T16:58:47+01:00Margarethe Maierhofer-Lischka[STORY] as ProKo, I want a confirmation dialog when using the "re-activate" button, so I cannot reactivate a show by mistakeDe- and re-activating of a show is a critical action. Currently, only the deactivation function offers a confirmation dialog to prevent user mistakes. During the testing cycle 12/23-1/24, users from Freirad suggested to also add a confir...De- and re-activating of a show is a critical action. Currently, only the deactivation function offers a confirmation dialog to prevent user mistakes. During the testing cycle 12/23-1/24, users from Freirad suggested to also add a confirmation dialog for the re-activation, to have consistency in the UX and prevent ProKos from doing mistakes.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/234Bug: The dashboard version is not visible anymore, helping with bug reports2024-02-14T10:56:51+01:00David TrattnigBug: The dashboard version is not visible anymore, helping with bug reportsThe status bar with the current dashboard version is not available anymore.
While there is no need to display the version on every page, there should be at least some place we user can check the version.The status bar with the current dashboard version is not available anymore.
While there is no need to display the version on every page, there should be at least some place we user can check the version.1.0-alpha3 — Playful Platypus ▶️🦦https://gitlab.servus.at/aura/dashboard/-/issues/99Calendar week display2022-09-09T19:43:55+02:00Stefan NussbaumerCalendar week displayWhen you visit the calendar by going to http://localhost:8080/calendar (or wherever your calendar is installed) you'll see the weekdays of the current week displayed in the first row of the calendar view:
![calendar_table_header](/upload...When you visit the calendar by going to http://localhost:8080/calendar (or wherever your calendar is installed) you'll see the weekdays of the current week displayed in the first row of the calendar view:
![calendar_table_header](/uploads/726d4a54a357ef649d42e19f2f8d7b5d/calendar_table_header.png)
Move forward by clicking right arrow button until you reach next month button. Click on right arrow button again. You'll see the week displayed in the calendar header stays at the week when the month changed, no matter if you click back or forth - it's frozen:
![calendar_table_header_wrong](/uploads/9293bd7fdce6556893b1cc1aa702e430/calendar_table_header_wrong.png)1.0-alpha2 — ⚖️🐦 Precise PheasantKonrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/83development-installation: user not found in storage2024-03-14T19:12:23+01:00Ingo Randolfdevelopment-installation: user not found in storagei have seen 2 errors when trying to log in to the dashboard with a local development installation.
this error reported here occurred after removing all relevant docker images and a re-init of aura-web.
loading the page shows this in th...i have seen 2 errors when trying to log in to the dashboard with a local development installation.
this error reported here occurred after removing all relevant docker images and a re-init of aura-web.
loading the page shows this in the console:
```
UserManager.getUser: user not found in storage 2 oidc-client.min.js:1:2013
```
clicking "Anmelden" shows:
```
MetadataService.getMetadata: No authority or metadataUrl configured on settings oidc-client.min.js:1:2273
error oidc-client.min.js:1
getMetadata oidc-client.min.js:1
_getMetadataProperty oidc-client.min.js:1
getAuthorizationEndpoint oidc-client.min.js:1
createSigninRequest oidc-client.min.js:1
_signinStart oidc-client.min.js:47
(Async: promise callback)
_signinStart oidc-client.min.js:47
signinRedirect oidc-client.min.js:47
signinRedirect auth.js:196
D vuex.esm.js:847
dispatch vuex.esm.js:512
dispatch vuex.esm.js:402
signIn App.vue:122
VueJS 43
56d7 main.js:43
Webpack 6
```1.0-alpha4 — Raving Raccoon 🤪🦝https://gitlab.servus.at/aura/dashboard/-/issues/80Display emission on the show overview page in descending order2023-10-20T12:29:11+02:00David TrattnigDisplay emission on the show overview page in descending orderAs discussed in the meeting on Nov 4 2020 and on Dec 15 2020, something similar to the following:
Display emissions in descending order by their date
- 4 emissions after the next emissions (not only the current day)
- 1 next emission d...As discussed in the meeting on Nov 4 2020 and on Dec 15 2020, something similar to the following:
Display emissions in descending order by their date
- 4 emissions after the next emissions (not only the current day)
- 1 next emission due (somewhat emphasized)
- 5 past emissions (somewhat grayed out)
This should be the default view when entering the page. Using the filter it's of course possible to get more emissions of the past and the future, if required.Aura 0.9Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/52Displayed version in UI should be read from "package.json"2020-10-12T16:49:31+02:00David TrattnigDisplayed version in UI should be read from "package.json"This should help improving the Software Configuration Management process.This should help improving the Software Configuration Management process.1.0-alpha2 — ⚖️🐦 Precise PheasantRichard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/215Episode Detail View: Improve order of form elements2023-11-08T17:52:12+01:00David TrattnigEpisode Detail View: Improve order of form elementsParent: https://gitlab.servus.at/aura/dashboard/-/issues/149+
---
The form elements should be ordered and grouped by their usage:
- Title
- Summary: This is high priority, since it is used for all excerpts on the website
- Content
- Li...Parent: https://gitlab.servus.at/aura/dashboard/-/issues/149+
---
The form elements should be ordered and grouped by their usage:
- Title
- Summary: This is high priority, since it is used for all excerpts on the website
- Content
- Links
- Image
- Hosts
- Tags should be at the end of the form: Tags have currently least priority, since this is only preparation for the coming CBA uploader and AURA search index.
### Screenshot
![image](/uploads/a8f1a54ac59e959800386946add5ecec/image.png)1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/84File Manager UI display "fileManager.noFilesAvailable" instead of relevant me...2022-01-14T16:53:28+01:00David TrattnigFile Manager UI display "fileManager.noFilesAvailable" instead of relevant messageWhen no Files are uploaded yet "fileManager.noFilesAvailable" is displayed. Display a message instead.
![image](/uploads/b3010ce446c420091b342c343d264f35/image.png)When no Files are uploaded yet "fileManager.noFilesAvailable" is displayed. Display a message instead.
![image](/uploads/b3010ce446c420091b342c343d264f35/image.png)1.0-alpha2 — ⚖️🐦 Precise PheasantDavid TrattnigDavid Trattnighttps://gitlab.servus.at/aura/dashboard/-/issues/266introduce comma separation for keyword entry in episode editor page2024-02-16T16:15:53+01:00Margarethe Maierhofer-Lischkaintroduce comma separation for keyword entry in episode editor pagewhen entering tags / keywords in the episode editor page, users have to push ’enter’ after each entry. entering several keywords with a comma in between saves the whole string (see screenshot). as a UX improvement, the dashboard could of...when entering tags / keywords in the episode editor page, users have to push ’enter’ after each entry. entering several keywords with a comma in between saves the whole string (see screenshot). as a UX improvement, the dashboard could offer comma separation for the keyword entry.
![Screenshot_from_2024-02-16_15-31-41](/uploads/2f421ee2e0068a5b82ddad33ce61addb/Screenshot_from_2024-02-16_15-31-41.png)https://gitlab.servus.at/aura/dashboard/-/issues/18load meta infos only at startup/login or when showmanager is activated?2023-11-09T14:28:31+01:00Andrea Ida Malkah Klauraload meta infos only at startup/login or when showmanager is activated?currently we use a huge amount of separate requests to get all the info needed in the show manager (e.g. loading all categories every time we switch to a new show). this is quite fine for a local setup, but it might get laggy when workin...currently we use a huge amount of separate requests to get all the info needed in the show manager (e.g. loading all categories every time we switch to a new show). this is quite fine for a local setup, but it might get laggy when working a remote connection (e.g. via mobile).
should we use certain infos (like show types, and other meta categories) only once, when a user logs in, or only when we switch to the show manager, but not every time we switch to a new show?1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/204Login button appears twice2023-11-07T13:24:41+01:00Margarethe Maierhofer-LischkaLogin button appears twiceParent: https://gitlab.servus.at/aura/dashboard/-/issues/103+
---
On the Aura login page, the login button appears twice - in the center area and in the sidebar menu. Both buttons work fine but it adds a bit of confusion for the users.Parent: https://gitlab.servus.at/aura/dashboard/-/issues/103+
---
On the Aura login page, the login button appears twice - in the center area and in the sidebar menu. Both buttons work fine but it adds a bit of confusion for the users.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/198long show titles exceed frame of the Show Selector2023-11-07T13:23:39+01:00Margarethe Maierhofer-Lischkalong show titles exceed frame of the Show SelectorParent: #103+
---
Some radio shows have long titles. Currently, the Show Selector bar displays the whole show title, which results in an overflow of text in the Dashboard header (see screenshot). It would be sufficient for the users to s...Parent: #103+
---
Some radio shows have long titles. Currently, the Show Selector bar displays the whole show title, which results in an overflow of text in the Dashboard header (see screenshot). It would be sufficient for the users to see an abbreviated show title, e.g. with three dots, so the show title does not exceed the Selector bar.
![Screenshot_from_2023-10-03_16-04-03](/uploads/212bdd8eeeab50b482dbc74d796d9c6c/Screenshot_from_2023-10-03_16-04-03.png)1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/56Move from modals to something less constrained2023-11-09T12:25:49+01:00Richard BlechingerMove from modals to something less constrainedParent: https://gitlab.servus.at/aura/dashboard/-/issues/103+
---
Currently we are primarily using modals as part of our UX strategy. While modals are nice for simple forms, they feel rather constrained for use cases that involve comple...Parent: https://gitlab.servus.at/aura/dashboard/-/issues/103+
---
Currently we are primarily using modals as part of our UX strategy. While modals are nice for simple forms, they feel rather constrained for use cases that involve complex data, since we essentially give up half of the screen space we have available to us. This also tends to make it difficult to display complicated tables with lots of actions.
Perhaps we could move to a more page-based/inline approach in dealing with editable data. Thanks to the dashboard being built in Vue the act of changing between pages is almost immediate, but it would allow us some more breathing space for designs/complex forms.1.0-alpha3 — Playful Platypus ▶️🦦Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/57Permission managment for adding playlist entries of type "Stream"2024-01-23T17:17:53+01:00David TrattnigPermission managment for adding playlist entries of type "Stream"Parent: https://gitlab.servus.at/aura/aura/-/issues/156+
---
To avoid the possible issue of constant licensing problems or RMs avoding to produce original content it could be helpful to implement following:
* By default only allow addi...Parent: https://gitlab.servus.at/aura/aura/-/issues/156+
---
To avoid the possible issue of constant licensing problems or RMs avoding to produce original content it could be helpful to implement following:
* By default only allow adding streams to playlists by Programme Coordinators
* Other users might be able to do that too, if they got the releveant permission assigned (via Steering)1.0-alpha3 — Playful Platypus ▶️🦦https://gitlab.servus.at/aura/dashboard/-/issues/65Provide selection for "Default Schedule Playlist" playlist2023-11-21T11:37:32+01:00David TrattnigProvide selection for "Default Schedule Playlist" playlistDiscussion needed where to put it.
This was previously known as "Schedule Fallback Playlist".Discussion needed where to put it.
This was previously known as "Schedule Fallback Playlist".Aura 0.9Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/55Refactor vuex store actions to use async/await2024-01-17T14:56:10+01:00Richard BlechingerRefactor vuex store actions to use async/awaitThe vuex store actions currently use a callback-based approach to deal with code that needs to execute after a certain action has handled. This can lead to strongly indented code that can be somewhat hard to follow.
Thankfully JavaScrip...The vuex store actions currently use a callback-based approach to deal with code that needs to execute after a certain action has handled. This can lead to strongly indented code that can be somewhat hard to follow.
Thankfully JavaScript introduced the :sparkles: magical :sparkles: feature of `async/await` as part of ES2017 which allows us to refactor these kinds of constructs into a more simple shape of:
```js
async function foo() {
try {
const result = await this.$store.dispatch("someAction")
// ... Do something with result
} catch (e) {
// ... Handle error
}
}
```
As the callback approach is spread pretty far across the codebase this will probably take a while to do and an incremental adoption might be advisable.1.1Richard BlechingerRichard Blechingerhttps://gitlab.servus.at/aura/dashboard/-/issues/249rename fields in the Show Area2024-03-11T03:00:23+01:00Margarethe Maierhofer-Lischkarename fields in the Show AreaFor details see the spreadsheet on terms to update.For details see the spreadsheet on terms to update.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldthttps://gitlab.servus.at/aura/dashboard/-/issues/241Show - General settings: improve layout, grouping, presentation of form fields2024-03-11T03:00:42+01:00David TrattnigShow - General settings: improve layout, grouping, presentation of form fieldso94 Feedback:
> Ev. könnten die Felder in ein paar Blöcke strukturiert werden, im Moment schwimmen sie je nach Länge der Feldbeschriftung und durch die unterschiedliche Größe je nach Inhalt recht unruhig und unübersichtlich.
Restructur...o94 Feedback:
> Ev. könnten die Felder in ein paar Blöcke strukturiert werden, im Moment schwimmen sie je nach Länge der Feldbeschriftung und durch die unterschiedliche Größe je nach Inhalt recht unruhig und unübersichtlich.
Restructure form to have more logical and visually balanced blocks.1.0-alpha3 — Playful Platypus ▶️🦦Konrad MohrfeldtKonrad Mohrfeldt