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 6 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.1

  • 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.



  • No labels