ALM: User Guide

Working with the backlog and Requirements

• Added the AI feature "generate a title", which builds a title from the text of a user story, Issue, or enhancement so that the title reflects the meaning of the text. This is especially useful when processing a stream of user requirements whose author did not pay much attention to the title. The operation is available for a single story and for a group, through a bulk operation.
• Added an AI feature that generates a PlantUML class model from the text of a user story or Requirement. Select text in the editor and choose "PlantUML class diagram" in the context menu. Use this feature to draft a PlantUML class diagram from a text description. The more detailed and rich the description, the better the model.
• Added an AI feature that generates Release notes, "Digest: what was done for the selected items". The feature is available as a bulk operation on user requirements (stories, Issues, enhancements), and as an action for an Iteration and a Release. The language model collects descriptions of implemented enhancements and stories, then produces a compact description of what was done.
• Using the results of the ALM RAG mechanism, the system automatically suggests traces between project artifacts along key links: Requirements on Issues, test and operational documentation, and so on. An auto-trace is not applied automatically; the user must validate it. The system indicates potential traces (auto-traces) so the user can link artifacts as they see fit. For details, see [D-14522] Auto-traces
• The project settings now include an "AI interaction settings" module. It lets you refine prompts and give the language model special instructions so the answer matches your tasks.

Organizing support

To reduce the effort of technical support engineers and shorten response and resolution time for user Requests, a feature was added that suggests a solution for a Request using AI features. To use it, ALM must be configured to work with an LLM (local or external).

When you work with Requests, on the "AI: request solution" tab the AI drafts a reply based on how previous requests were resolved, knowledge base articles, and product documentation. For details, see [D-14503] Processing Requests

Test management

• On test report and test forms, the "Duration" field shows how the duration differs from the previous run. In table views you can place the deviation in a separate column and use it in filters or charts. A duration that differs from previous runs can indicate several problems, for example:
  • low tester productivity, for manual testing;
  • slower application performance, for automated testing;
  • problems with the environment or with how the application runs in a specific environment (a different DBMS, a different OS, and so on).
• With a language model (LLM) integration configured, you can quickly generate test documentation text from Requirements. Because test documentation varies (step-by-step scenarios, acceptance, Gherkin, and so on), generation also differs by test documentation type. In the test documentation type settings you can specify which documentation format matches that type. For details, see [D-14418] AI capabilities

Development management

The "File statistics" module was added to track metadata related to source code files. The base set of stored data includes:

• the total number of lines in the file;
• the number of lines covered by tests;
• the percentage of code covered by tests;
• the programming language.

You can extend the attribute set with custom metadata and create links to source code files — for example, to bind Requirements directly to files (an alternative or addition to links between Requirements and commits). For details, see [D-14417] File statistics

Project and resource management

• Boards for Issues, enhancements, and Tasks now have a switch in the upper right (next to the green buttons). Use it to show or hide dependencies between cards. Dependencies are shown as arrows. This visualizes links such as blockers and other dependencies on the board, so you can plan work on the cards with those dependencies in mind.
• Modules were added to visualize and export task workload data at the role level — "Workload by role" — and at the team level — "Workload by team". These are aggregated workload figures for tracking load and overload by project role or by team (resource pool).

Automation

• Custom action settings now let you specify parameters. When such a custom action runs, the system opens a window asking for those parameter values. You can substitute the values the user enters into the Webhook address or body, or use them inside the PHP script that runs as a result of the action. For details, see [D-7418] Custom actions
• Events related to custom actions (Webhooks, scripts, and so on), scheduled actions, and AI interactions are recorded in the event log. The event log is available in the administration section and directly in the project. The project event log shows only events created inside that project.
• Automatic actions can now assign a watcher.

Controls

• Tree selection is now available in "Multiple choice" controls for custom attributes.
• For files that are not images, the context menu offers: download, open, or edit. "Open" opens the artifact view form with the file, where a preview is available together with file attributes such as version, author, and so on. You can view a PDF, MS Word document, or 3D model without downloading the file and without installing extra viewer software.

System settings

• In the administration section, application settings now include "Cookie lifetime" for the cookie that stores the user session identifier. When the cookie lifetime ends, the user must authenticate again.
• You can configure estimation scales: adjust existing ones or create your own. Go to Administration, Settings, Lookups. Open the "Estimation scales" lookup and edit the system scales or create new ones. The "Hour equivalent" field maps a complexity estimate to the time needed to implement a story or Issue. The hour equivalent of an estimate is used to plan the implementation dates of a story from the estimate that was entered.