Skip to content

Conversation

@MariekeGO
Copy link
Member

No description provided.

@MariekeGO MariekeGO self-assigned this Jan 13, 2026
@MariekeGO MariekeGO marked this pull request as ready for review January 14, 2026 06:39
@MariekeGO MariekeGO requested a review from a team as a code owner January 14, 2026 06:39
Copy link
Member

@AndreRodriguesSkyline AndreRodriguesSkyline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added a few suggestions.
In general, it would probably be easier to indicate in the text that the ticketing module is obsolete as of version 10.6.0, or when using STaaS, no?

>
> - `GRANT CREATE ON ALL KEYSPACES TO <YOUR DATABASE USER/ROLE>;`
> - `GRANT ALL ON KEYSPACE "SLDMADB" TO <YOUR DATABASE USER/ROLE>;`
> - `GRANT ALL ON KEYSPACE "sldmadb_ticketing" TO <YOUR DATABASE USER/ROLE>;`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting from RN44417 (the server changes, not yet pushed), the "sldmadb_ticketing" schema is no longer created automatically if it does not exist.
So, maybe add a note indicating that is obsolete from 10.6.0 onwards

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We usually don't document release notes as long as the main and feature release versions are still set to TBD, so I'd prefer not to include changes for 44417 within the same pull request. I'll add a reference to 44417 in comment here, so we can add the note with a separate pull request as soon as 44417 is merged.

#### Modules \> Ticketing Gateway \> UI available

Permission to access the *Ticketing Gateway* app.
Permission to access the *Ticketing Gateway* app. Obsolete as of DataMiner 10.5.0 [CU11]/10.6.0.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the ticketing module will no longer be supported from 10.6.0.0 main release onwards, maybe the "DataMiner 10.5.0 [CU11]" can be removed.
The same applies to other locations where this text is present.

Copy link
Member Author

@MariekeGO MariekeGO Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RN 44371 and 44373 also mention 10.5.0 [CU11] as main release version, so doesn't this mean that users who stay on the 10.5.0 CU track will also not be able to use Ticketing anymore? I suppose under the hood it will still be available until 10.6.0, but if users can't actually see the app or any of its functionality anymore in Cube and the web apps, I think mentioning 10.5.0 [CU11] here as well would be better.

# Using the Ticketing Gateway API

> [!IMPORTANT]
> The Ticketing Gateway API is obsolete. It is no longer available from DataMiner 10.5.0 [CU11]/10.6.0/10.6.2 onwards.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not related to Cube/Web funcionality, so it will only be deprecated with RN44417 (the same for the files below).
So, if you want, you can say "It is no longer available from 10.6.0 onwards.", and also mention that is not available when using STaaS

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this will only be deprecated with 44417, I think it would be better if we only mention that it is no longer available as soon as 44417 is merged, just in case the versions still change from what is planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants