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 11 Next »

Mostly a technical release

2.6.0 is a major version because we have upgraded a lot of our libraries. There is slightly-higher-than-usual probability of breaking with some versions of Confluence/Jira, although we have tested every major version.


The custom field is available by default in Jira

In Jira, the "Requirement Yogi Links" custom field was only available to non-Data-Center versions by default. It is not available for everyone.

  • JQL works!
    • Example: RequirementCustomField = 'REQ-002' (the name depends on the name you provided for this field),
    • Example: RequirementCustomField in requirementYogiKeys("REQ-%")
    • See: JQL Syntax
  • If you have already created a custom field, you need to upgrade the "searcher" to be able to use JQL. See screenshot below.

New layout for the Jira dialog

As highlighted in Jira links, we have refactored the Jira dialog to accomodate for an infinite number of baselines:

Removed

  • We have removed the "display mode" field form the RY Report macro, since it didn't work and no-one noticed it for 2 years.
  • In the traceability matrix, it is not possible anymore to display the status of a Jira issue in the same cell. You must add a new column for the "status" field.

More issues resolved in 2.6.0

In order of relevance:

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
     Test & Compliance module: Can now work without Requirement Yogi,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Jira: Activate the custom field by default,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Jira: The issue is reindexed when the custom field is modified,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Bug when creating a baseline and a page was in draft,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Coverage matrix: Ability to work cross-spaces,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Scaffolding compatibility: Pages are now reindexed when a Live Template is updated,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix export to Excel: Requirements are now links, so it is easier to navigate between Excel and Confluence,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Library upgrades (technical issue without user-facing feature),
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Removal of the "display mode" in the RY Report macro.

Resolved in 2.6.2

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Main improvement: Overhaul of the timeouts for the queue in Jira. See Queue performance for all explanations.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Add a 30s timeout for the deletion of items in the Jira administration, so the user can have some feedback,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fixed the upgrade task in Jira, which was causing a message in the logs,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Ability to delete the requirements which were on an Excel file, when the Excel file was removed.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix the traceability matrix for Safari,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix the space tree for IE,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix the link to the definition of requirements, which was malformed.

Resolved in 2.6.3

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  In the Jira dialog, changed the UI to allow an infinite number of baselines (see screenshots). Added a "Criteria" field to replace the two "Space" and "Baseline" menus, to enable an infinite number of baselines. It also allows upgrading/downgrading requirements to the provided baseline.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  In Jira, an "Expand all" button
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Add a separate role to rename requirements
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  In the baseline refreeze, the "Add dependency" button only added the examples, not the whole list of dependencies. This also enables more requirements in a refreeze
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix the export-to-Excel function, which requires a specific version of a library
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Ability to use a traceability matrix for the baseline blueprint, so customized columns can be displayed
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Ability to change the owner
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Support for the "single select" custom field in Jira
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Support for the "multiselect" custom field in Jira
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Display "Load more..." when it is needed

Resolved in 2.6.5

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Major: Change the primary key for the table "Queue" (from int to long). PostgreSQL administrators can choose to migrate the type manually.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Major: Change of behavior, deleting a requirement will not remove the links in Jira. It will only hide it in Jira, assuming v2.6.5 is installed on the Jira side too.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Remove the name of the requirement, if it is at the beginning of its own text.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Screen to repair Jira links: Support moved issues
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Support for the Handy Status macro
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Traceability matrix: Ability to choose to display all links in separate/same cell
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix the Jira Bulk Issue Creation, "Hide synchronized" tickbox
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  HTML exports: Link to another file, instead of linking back to Confluence,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Editor / "Tranform definitions to links": Ability to transform all definitions except the first one for each requirement,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Technical detail: Use a specific LIKE clause for SQL Server with escapable characters (only impacts the Baseline service),
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Fix upgrade tasks V50 and V51 (mid-2020) for MySQL,
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Reduce the size of the .jar file, from 5.5MB to 3.3MB.
  • In Jira:
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Add a link to the app in "Manage addons"
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Support for deleted requirements on the Confluence side,
    • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Requirement text is not retrieved when set through the custom field 


  • No labels