You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have already thought about this as well, but I was/am against it. Reasons:
A reports is often context specific and special titles, descriptions, ... are needed. So report templates may not be so much reusable
Creating a report template with e.g. charts costs a lot of dev-time.
The template may depend on the used projects and its configuration
I think somebody would be much faster, if he/she gets the data into excle and co. quite easy, and is then able to work with it.
Therefore the csv export was added, to make this possible.
So I would like to close this issues, as I don't think that investing time into this topic is gainful (as long as there are other feature/bugs open)
The template-development itself costs a lot of time, but providing a general solution/interface (without a complex template) does not.
So we could support this with a very basic template.
And maybe in future somebody writes a better one.
To be able to later publish and view it (e.g. in a build pipeline).
The text was updated successfully, but these errors were encountered: