Category: Application

Some QCD indicators are not updated after the change of month

Issue Symptoms

You are experiencing an issue when you change the month on a QCD Board, not all indicators update to reflect the previous month. You've tried changing the months and reconfiguring the table, but unfortunately the problem persists.

Cause

The problem you are experiencing is related to the creation of the period in advance.

Once a period has been created (i.e. accessed via the “Change period” menu), its configuration is instantiated from the configuration of the period you're in, and will no longer be modified if you make changes to the initial period.

In the case of a period that has not yet been instantiated, the configuration of the current period will be the same for the new period.

Existing periods are visible in the QCD utility > “View data history”. This behavior is also indicated in the period change window (QCD Utility > Month change).

Solution

A workaround is available in versions 4.20 and higher.

(Optional) Export the board to roll back just in case of an error.
Return to a previous period (containing the desired configuration of indicators)
Select the period which has the wrong indicator configuration from the QCD utility > View data history > Manage data history
Delete by clicking on "Delete data history selected"

Instantiate the month period, which should now have the correct configuration

If you're not at version 4.20 for this workaround or on a supported version, we recommend that you upgrade iObeya to a supported version in order to benefit from it as well as the new features and latest bug fixes.

Support

If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

ApplicationQCD

Some QCD indicators are not updated after the change of month

Issue Symptoms

In a weekly frequency board, I can't launch the consolidation on the first week of 2025.

The calendar used to select the period displays dates at the end of 2025 and beginning of 2026, making it impossible to select the first week of 2025.

Solution

To get around this problem, you can use the following URL, replacing the variables with those corresponding to your case:

In a text editor modify this request:
```
{SERVER_URL}/s/servlet/qcd/api/consolidation/launch?type=boards&ids={BOARD_ID}&startDate=30-12-2024&endDate=05-01-2025
```
by replacing the {SERVER_URL} variable by the URL of your iObeya instance and {BOARD_ID} variable by the ID of your board
Open a new browser tab
Copy/Paste the URL you created in step 1 and launch this URL.

The consolidation of your board should work properly.

Support

If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

QCD

Some QCD indicators are not updated after the change of month

Issue Symptoms
When I load a board, I always have to connect to the third-party application in order to display it in the webcontent. If I reload, change board, I'll have to connect again each time.

Solution

The problem is due to the blocking of third-party cookies.

To check, go to the cookie management of your browser
If third-party cookies are blocked, you can create an exception for your iobeya platform.

Support
If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

ApplicationWeb content

Some QCD indicators are not updated after the change of month

Issue Symptoms

When embedding Microsoft content (such as Excel or Power BI) in iObeya, although already logged in, it may display "Please login" instead of the content.

Solution

First of all, it's imperative that cookies are authorized: without authorization, iObeya won't be able to correctly share authentication with Microsoft content.
Then you need to open the content again, which may require a new login.

After that, the content should display correctly.

This process may need to be repeated in the future. This problem is linked to the way Microsoft handles authentication cookies.

Support

If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

ApplicationWeb content

Some QCD indicators are not updated after the change of month

Issue Symptoms
Despite several attempts to connect to my instance, it tells me that the instance is still not connected.

Solution

Check the instance url used
The instance url must match the name of the organization without the desired project.
If the desired project is in the url, the connection will not succeed.
Check information entered during connection
After clicking on the instance not logged in, a new page should open.
Check that the information entered is correct and that the "Authorization HTTP Header" field is set to Basic.
Check the rights applied to your PAT
If the rights applied to the PAT are insufficient, you may encounter other problems when importing cards or loading card content.

Related documentation :

Support
If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

ApplicationAzure Dev Ops

Some QCD indicators are not updated after the change of month

Issue Symptoms

The "Story Points" field is not displayed on iObeya (Jira cards)

Solution

The fields that appear in iObeya (Jira Cards) are fields that are on the Jira project creation screen.

If the "Story Points" field is not included in the Jira project (Agile) creation screen , it will not be configurable in iObeya.

When creating a Story/epic, make sure that the "Story Points" field is present in the issue creation popup.

A Jira administrator has the ability to configure the creation, display, and editing screens for each Jira project

Support

If you require assistance to resolve the problem, please reach out to support@iobeya.com

ApplicationJira

Some QCD indicators are not updated after the change of month

Symptoms

When manually modifying the iteration dates or names of sprints on Azure, the changes will not reflect on the iObeya Azure board (Sprint)

Solution

In order to apply the changes made in Azure to the iteration dates and/or sprint names to iObeya Azure board (Sprint), a new Azure board needs to be created.

This is because the synchronization only takes place during the board creation process.

Support If you need further assistance, please contact the iObeya Support.

Azure Dev Ops

Some QCD indicators are not updated after the change of month

Symptom of the problem:

The content of my Azure card does not load or loads indefinitely

Solutions :

Check the rights assigned to the PAT used
It's advisable to create a "Full Access" token to confirm that the problem is really linked to the token.
Check the url of the instance used
If the url used is not properly instantiated, content of the card will not load.

Related documentation :

Support :
If you need help solving the problem, please ask for assistance. (See Support request)

Azure Dev Ops

Some QCD indicators are not updated after the change of month

Issue Symptoms

Some icons of the software are missing, like toolsets, stickers. It may happen when a problem occured during the start of the application.

Solution

To regenerate the missing icons you have to follow this procedure. If possible test on your pre-production beforehand:

Stop the Tomcat service

Run the following command on your database:

update asset_collection_items set version = null;

If this request does not result in an error, you can start your Tomcat

Support

If you require assistance to resolve the problem, please ask for support. (See Help section)

Application

Some QCD indicators are not updated after the change of month

Issue Symptoms

When trying to access a QCD board, the board gets stuck on a grey screen and indicates that the consolidation is in progress.

After a few minutes, the board is still blocked and the consolidation does not seem to be successful.

It is then no longer possible to access the contents of the board.

Solution

If you are in a version of QCD < 4.17.2 please contact the support team (support@iobeya.com) with your iObeya version number.

If you are in a version of QCD > 4.17.2 you can use the following procedure:

Access the blocked QCD board
Go to the URL field of your browser where the URL of your board is located.
This URL is of the form :
SERVER_URL/s/download/resources/client-html-plugin/version/public/#/fr/board/BOARD_ID
Replace the following section of the URL :
/s/download/resources/client-html-plugin/version/public/#/fr/board/
by
/s/servlet/qcd/qcdaddon/consolidation/?method=reset&boardId=
Your URL will then be:
SERVER_URL/s/servlet/qcd/qcdaddon/consolidation/?method=reset&boardId=BOARD_ID
Launch the URL

The consolidation in your board should unblock and you can restart it.

Support
Please contact the support team if you have any questions about this procedure by sending an email to support@iobeya.com.

ApplicationQCD