[Feature request] Minor thing - naming of the downloaded report

[olw-medcom]

Hey there,

A minor thing:
Currently when I download a report from the ITB, the filename is always just 'report'. Which in practice results in my downloads folder containing these files:
report.pdf
report (1).pdf
report (2).pdf
..
report (55).pdf

It can be a bit confusing. Would it be possible to make the name of the report the test case name? Or in the case of a test suite report, then the name of the test suite? I'm not sure what to do in the case of a conformance report, maybe the name of the system?

Best regards

[costas80]

Hi @olw-medcom. I'm not too keen on naming the reports using text that is not controlled by the ITB (i.e. user-provided names). An alternative approach could be to name each report based on its type (e.g. "test_case") with a date postfix. Would that still be an improvement for you?

[olw-medcom]

Hey @costas80, ahh right I understand. Unfortunately no that wouldn't really be an improvement, atleast not currently. I will let you know if we in the future would prefer it

[costateixeira]

would it make sense to have the filename structure as a global parameter? once set for an ITB instance, users can't change it.

• report.pdf
• test_case-{yyyy-mm-dd}.pdf
• DK-report-{suite}-{system}.pdf
  -...?

[olw-medcom]

I mean yes that would improve it a little bit, but I am guessing @costas80 still is hesistant because it is user input

[costas80]

would it make sense to have the filename structure as a global parameter? once set for an ITB instance, users can't change it.

Interesting. We had discussion about a loosely linked topic here (about date formats). I am thinking however that if we do allow configurable report naming, this is done in the community's report settings (accessible from the community management):

We could provide here an option to customize the report name depending on the report type (with reasonable defaults). Like this we also avoid taking an odd general approach for cases like the one mentioned by @olw-medcom:

I'm not sure what to do in the case of a conformance report, maybe the name of the system?

It would then be up to the admin of the community to name appropriately their reports. I am still not a fan of using user-provided data for file names (test case name, test suite name, system name) but that is up to the community admin to manage (by default such information will not be included). Also, if we do support user-provided data in file names the ITB can ensure that these are sanitised (e.g. no path traversal characters and other nasty stuff like that).

One potential issue is if you have organisations from different countries in your community with some defining their systems in e.g. French, others in Greek, and others in Polish. If you have configured report names to include system or organisation names you could end up with reports that vary wildly (although still this is a matter of configuration).

[costas80]

Ok I think I'll reopen this issue and add it to the backlog.

We'll foresee a report naming configuration option in the report settings per report, that will support placeholders as applicable per report type. On the ITB's side we'll just need to put in some safeguards to ensure that the resulting report names are OK (e.g., sanitized security-wise, not too long, odd characters replaced etc.).

[costateixeira]

this would be admin input only - set in the docker config, I guess. User would have no input into that

…

On Fri, Mar 6, 2026 at 9:43 AM Oliver Winther (MedCom) < ***@***.***> wrote: *olw-medcom* left a comment (ISAITB/gitb#179) <#179 (comment)> I mean yes that would be awesome, but I am guessing @costas80 <https://github.com/costas80> still is hesistant because it is user input? — Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3HUUBIHQPDFOJOPBOAV234PKFR5AVCNFSM6AAAAACWIIJY5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMJQGM3TEMZUG4> . You are receiving this because you commented.Message ID: ***@***.***>

[olw-medcom]

Great news!

[costas80]

this would be admin input only - set in the docker config, I guess.

A setting in the Docker config (i.e. environment variable) is really for very basic/core stuff. If this is a system-wide setting it would be included in the System administration panel so that the Test Bed admin can configure it visually and have it apply without restarts. Ideally we would eventually want all things configured via the UI unless it's very core information (e.g. the type of SSO you use).

Given that this is configuration is linked to reports, and we have a dedicated screen where reports are customised per community, It seems to be sensible to manage this from there. The only slightly odd side-effect is that if you are connected as the Test Bed admin you may get different report names if these are produced for different communities. Also, you could always in theory run tests as the Test Bed admin, making it unclear what report naming will be used there...

I think the most complete approach would be treat this as a two-level configuration (like landing pages):

• System-wide configuration defined in the system settings. This applies to the Test Bed admin and also serves as the defaults for communities that have not specified their own naming convention.
• Community configuration (as part of the report settings), where the community admin can either choose to use the inherited default settings or customise for the community).

In cases where an organisation is running the ITB with one effective community (i.e. not a multitenant case), you would basically configure this in the system settings and skip overriding it in the community settings. Like that the Test Bed admin sees the same report names as everyone else.

I think this approach covers all cases nicely :)

[olw-medcom]

I agree @costas80