Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

New features

Note to administrators

  • Do not downgrade below 3.5.0 after upgrading to 3.5.x or 3.6.x.

  • We’ve reorganized the tabs in the space, including deleting two tabs,

  • We have a new Excel import, for properties,

  • Traceability matrices don’t display the Jira issue summary by default, users will have to add a new column.

New tabs for the space

  • The tab “Estimates” and “Excel” has disappeared,

  • There is a new tab named “Reports”.

  • There is a new tab “External properties”, which both display external properties and the Excel import for those external properties.

Why did we do that?

  • The “Excel” import wasn’t used by most companies, since it had two flaws. First, customers expected to edit requirements after they were imported, they were asking “Is there a Confluence page that I can edit, with those requirements?”. We ended up recommending customers to copy-paste their requirements into Confluence. Second, customers expected to edit existing requirements with this import, so we’ve implemented this in the new “External properties” tab. If you still need the Excel import, please tell us, and it is available in the footnotes of the “External properties” tab.

  • The “Estimates” tab wasn’t used at all, becuase the feature wasn’t properly polished. This is what we’ve done, and we’ve created the “External properties” tab.

New “External properties” tab

This tab lists the existing external properties. The hyperlink goes to a traceability matrix, with the external property in edition mode, so your users have a much faster way to start filling in those properties.

Second, notice the “Upload” button at the top: You can upload an Excel file and import values into those external properties. See next section.

The new Excel import

The new Excel import can be found in the “External properties” tab, because it imports data into external properties.

Here is the expected workflow:

Write requirements → Export to Excel → Send to your customer → Your customer adds comments and perhaps a validation status → You reimport the file → Read the comment on each requirement.

First step

Upload the file

Second step: Choose a template

Are you reuploading the file every week from the same customer? Just reuse the template that you have used last time!

Templates can be shared to the space; By default, they remain private to you.

Third step: Perform the mappings

Many things to see on this page:

  • Each column has a little menu where you can tell which external property to map this column to,

  • It is only possible to map “flat files”, i.e. lists of requirements and their status. It is not possible to import a traceability matrix with merged cells, since it means your data is disorganized.

  • The mapping for each column is visible in the gray box at the top of each column.

Capabilities:

  • Supports Excel files with several tabs,

  • You can add a template name, to perform next imports with the same template,

  • It can only import to external properties. Other properties are edited on pages.

New “Reports” tab

This list used to be hidden away in the sidebar (“View all”) or in a submenu of the traceability screen. Users reported that they couldn’t easily discover them, so here they are!

It shows all reports saved by your team, in 3 categories:

  • Private to you,

  • Shared by you,

  • Shared by your team.

Space administrators can view everyone’s private reports and reassign them, in case an employee leaves the company.

Other changes

Jira issue titles are not cached in Confluence anymore

https://requirementyogi.atlassian.net/browse/RY-1312

We used to copy the title of the Jira issue in Confluence, but that triggers issues about the permissions on those Jira issues. Since the OAuth / application links work well, we now only keep the issue key, and retrieve the Jira issue with the permissions of the current user.

Impact on the traceability matrix: The ability to display the Jira summary field in the same cell has disappeared. Customers will have to display a separate column, containing the Jira issue summary.

Properties in the traceability matrix: Resolved the “large menu” issue

https://requirementyogi.atlassian.net/browse/RY-1257

Users with a lot of properties had difficulties when inserting properties in the matrix, since the page snapped up and down when displaying the properties.

We’ve created a dialog box, so users can select their properties using the autocomplete.

Last note

We’ve created a mailing list, to tell you about new features, security vulnerabilities, and the community… , and the good news is that those categories are separated.

Go to https://www.requirementyogi.com/manage-profile/ to subscribe.

  • No labels