Major improvements:

• RY-480 Jira issues can be created in bulk from the search in Confluence. Support for large sets (beyond 100). Requires 2.3.2 on the Jira side.
• RY-275 The traceability matrix now supports a LOT of fields from Jira, including Jira-to-Jira links (several levels of depth into Jira), and including some Xray fields. The traceability matrix also supports drag-n-drop to reorder columns, double-click to rename, refresh without reloading the page, etc.

Minor fixes:

• RY-498 / RY-501 Ability to delete a link in Jira when the requirement doesn't exist anymore in Confluence.
• RY-502 Automatically upgrade the API version when displaying the RY administration in Confluence. Also, reorganize the welcome screen in the administration.

Major improvements:

• RY-480 Jira issues can be created in bulk from the search in Confluence. Support for large sets (beyond 100). Requires 2.3.2 on the Jira side.
• RY-275 The traceability matrix now supports a LOT of fields from Jira, including Jira-to-Jira links, and including some Xray fields (the plugin from Xpand IT).

Minor fixes:

• RY-498 / RY-501 Ability to delete a link in Jira when the requirement doesn't exist anymore in Confluence.
• RY-502 Automatically upgrade the API version when displaying the RY administration in Confluence. Also, reorganize the welcome screen in the administration.

• https://playsql.atlassian.net/browse/RY-511 There is a problem if requirements have been moved across spaces and they were linked to Jira. Please have a look at the bug report for more information, it requires action from the administrator.
• https://playsql.atlassian.net/browse/RY-509 Compatibility with EDM
• https://playsql.atlassian.net/browse/RY-506 Minor fix about a link in popups
• https://playsql.atlassian.net/browse/RY-503 Correction for the baseline refreeze

There will be another release soon with new features, we just wanted to deliver the bugfixes quickly.

• RY-511 There is a problem if requirements have been moved across spaces and they were linked to Jira. Please have a look at the bug report for more information, it requires action from the administrator.
• RY-509 Compatibility with EDM
• RY-506 Minor fix about a link in popups
• RY-503 Correction for the baseline refreeze

There will be another release soon with new features, we just wanted to deliver the bugfixes quickly.

Beware: There is a change in the behavior of the traceability matrix. Cells aren't merged anymore after a non-merged column. More details in the release notes. On the upside:

Beware: There is a change in the behavior of the traceability matrix. Cells aren't merged anymore after a non-merged column. More details in the release notes. On the upside:

• We can create Jira issues in bulk from requirements (see details),
• The traceability matrix now has a working pagination,
• The traceability matrix can now receive the significant improvements planned in the next releases.

See Release notes 2.3

• RY-492 The "rename requirements" feature didn't report errors properly from Jira
• RY-496 Make the traceability matrix, case-insensitive.
• Also, on request to the support, it is now possible to display the JSON editor in the traceability matrix, for advanced users.

• RY-492 The "rename requirements" feature didn't report errors properly from Jira
• RY-496 Make the traceability matrix, case-insensitive.
• Also, on request to the support, it is now possible to display the JSON editor in the traceability matrix, for advanced users.

Please plan to upgrade to Confluence 6.13 or above, before November. We follow Atlassian's Enterprise Releases, and support for Confluence 6.6 will be dropped in December.

• RY-459 Fix error when searching for requirements
• RY-456 Fix requirements displayed in red for 'include' and 'page-properties-report' macros.
• RY-395 Optional support for the version 2.2.5 used in Jira (namely, when resetting the links, it resets the whole requirements).

The Jira part of this release is the biggest. Please look at the release notes before upgrading the Jira side.

Please plan to upgrade to Confluence 6.13 or above, before November. We follow Atlassian's Enterprise Releases, and support for Confluence 6.6 will be dropped in December.

• RY-459 Fix error when searching for requirements
• RY-456 Fix requirements displayed in red for 'include' and 'page-properties-report' macros.
• RY-395 Optional support for the version 2.2.5 used in Jira (namely, when resetting the links, it resets the whole requirements).

The Jira part of this release is the biggest. Please look at the release notes before upgrading the Jira side.

• RY-441 Saved traceability matrixes couldn't be deleted,
• RY-450 Cross-space links were displayed in red

• Compatibility with Confluence 7
• RY-450 Cross-space links were displayed in red
• RY-441 Traceability matrix weren't deleted properly

• RY-443 Display an error message when attempting to delete a "orphan" requirement (a requirement with no page attached) if it belongs to a baseline.
• RY-442 and RY-449 Don't index any custom content provided by other plugins, except Confluence Questions, pages, blogs and comments.
• RY-440 Fix exception in some circumstances when attempting to use the "inline replacement" of requirements when viewing a page.

• RY-443 Display an error message when attempting to delete a "orphan" requirement (a requirement with no page attached) if it belongs to a baseline.
• RY-442 and RY-449 Don't index any custom content provided by other plugins, except Confluence Questions, pages, blogs and comments.
• RY-440 Fix exception in some circumstances when attempting to use the "inline replacement" of requirements when viewing a page.

See the notes related to the DC version: Requirement Yogi for Data Center

See the release notes for the version 2.2.x (one item to configure in the administration): Release Notes – 2.2

In addition to changing the metadata to show DC compatibility, we've fixed RY-279 (Inline replacement) in this minor version.

Fixed RY-440: There was an exception when replacing requirements inline. Also, this version is Data Center-compatible.

2 important points today:

• Administrators must provide a username in the Requirement Yogi administration (see the release notes).
• We plan on releasing a Data Center version of Requirement Yogi, and it will imply a price change for customers who upgrade. See the announcement.

The release notes are available at this address: Release notes 2.2.

The Jira version 2.2 will be published in a few weeks.

A lot of customers have requested to be able to write requirements in vertical tables. It is now possible, if you follow the correct layout.

• RY-428 Dependencies were not indexed properly.
• RY-427 Displaying fields of the requirement next to the links to this requirement didn't work.
• Also fixed the onboarding page, which didn't display.

• RY-422 The popup for requirements doesn't display in Internet Explorer / Excel.
• RY-423 Support Excel files with empty worksheets.

Note that RY-423 also needs the latest version of "PSEA", 1.5.3, for a complete fix.

We've removed a few deprecated features in this release and prepared the compatibility with the next (unreleased) version Confluence. This release contains important changes that could impact customers. Please review the release notes carefully. There is no "actual feature" in this release, only bugfixes.

Notably:

• All tabs are visible to everyone (We don't rely on the EXPORT permission anymore),
• Immediate synchronization with Jira is mandatory for everyone (We've removed the ability to postpone synchronization),
• We load the requirement popups after the page is loaded.

There are many upsides that are not immediately visible (forward compatibility, performance, gracious shutdown, etc).

• RY-417 The Traceability matrix was limited to 300 rows. Use the global limit instead.
• RY-388 Use the global limits for the Coverage and Dependency matrixes.

RY-416 Users of MySQL have been meeting an issue where there would be no results in the RY Report, or in the search.

• RY-396 If a requirement is still in state 'Active' despite the underlying page being deleted, mark it as 'Deleted'. It's a rare situation, because requirements are already marked deleted when someone deletes a page, but it could happen when deleting drafts or other documents.
• RY-386 In the editor, ensure the requirement matching exactly the user's entry is at the top of the list and visible.

See the release notes for all details: https://documentation.play-sql.com/display/RY/Release+2.0+-+Excel+import

• Excel import: It is now possible to attach Excel files to pages and mark them for importation.
• Global limit: We've introduced a way for administrators to determine the maximum number of requirements that can be viewed on a single page, imported from a single file, displayed in the traceability matrix, etc.
• Deprecation notice: In a future release, we won't require the "Export" permission to display the traceability matrix and other complex reports. See the release notes.

Yes, we're in a bugfixing spree right now, and some customers need those features fast. My apologies to those for whom 2 releases in 2 days incurs more work.

• RY-319 Specific indexing issue, where a link to the original page would be removed if the plugin was disabled when the requirement was removed. Also, fix reindexing for Firefox.
• RY-320 Display error messages in the Rename screen. They were hidden because of a bug.
• RY-321 Ability to process messages one-by-one for the queue of Requirement Yogi between Confluence and Jira.

• RY-314 Copy-pasting links to requirements from view mode to the editor, without using "Copy URL", results in the requirements not being properly reindexed.
• RY-302 Missing URL in the search results for baselines which were created with the "Instant Baseline" feature.

• RY-295 Inserting a macro in a cell creates two macros
• RY-293 Bug when removing a baseline
• RY-184 Better handling of duplicates. If you create two requirements with the same key, it displays them in red and suggests to solve it.
• RY-291 HTML tags are displayed as text (escaped twice) when one uses the feature of displaying a property in the link of a requirement.
• RY-290 Change the ordering of the list of requirements: The suggestions for new requirement keys now appear as first.
• RY-287 In the traceability matrix / Excel export, export the Jira status (when the Jira status is configured to be displayed).
• RY-286 In the Excel export, unescape the HTML of the requirements, in order to have actual text in Excel cells.
• RY-156 Feature to transform requirements into links-to-requirements in bulk. Necessary when copying a page.
• RY-278 Small bugfix to avoid requirements with no key.

• RY-277 When creating a baseline, suggest a name that doesn't exist already, suggest to freeze requirements immediately and show dependencies, if any.
• RY-278 In the space administration, a page to reindex the whole space if needed.

• RY-264 In the editor, let the user select which version of the requirement he wants to link to.
• RY-264 In the byline (the little popup at the top of pages when you click the icon next to the breadcrumbs), add a way to compare the requirements of the page to baselines. It is pretty cool, actually, check it out.
• RY-276 (Technical change) In the storage of requirement, an API was deprecated, so use the more modern one.

• RY-270 We've improved the UI of the diff and the algo - Now, dependencies on requirements which belong to the same baselines won't be counted as different if they are on the same baseline or on the latest version (even though it is technically a different version number). We've also added checkboxes to select which parts of the requirements should be compared (links, text, properties etc).
• RY-68 Instant baselines. It is now possible to create a baseline for the current page, from the little icon at the top of the page ("byline icon"). Such baselines don't have a summary page attached to it, so it is only possible to rename/delete them from the admin screen.

We're adding the ability to show the detailed differences between two baselines (or any query you like).

• RY-270 Add a diff tab in the search
• RY-273 The traceability matrix can now be saved/bookmarked, in addition to being inserted on pages,
• RY-267 Message queue for changes on requirements between Confluence and Jira,
• RY-274 Bugfix: Test sessions now work on baselines
• RY-243 A link is created in the Jira issue when it is mentioned in a test session along with a requirement.

If using the 3 modules (RY, Testing & Compliance and the Jira module) in the latest versions, then the Jira module MUST be upgraded to 1.13.0 too (otherwise a queue of technical messages will fill up).

As described in RY-268:

• Added a little icon in the byline of a page, for all documents with the labels "requirementyogi-blueprint", "ry-doc". This icon is a menu, where a user can reindex or open the search based on the current page.
• It seems there are a few bugs in the inline transformation, depending on the order one enters data in the fields, it ends up not finding the requirements on the page.
• Little bugfix in the traceability matrix : Lines were duplicated if showing two properties of the same requirement.

Read our release notes with images on this page!

• RY-256 If you use both Requirement Yogi and Testing & Compliance, then this version introduces the ability to create a Jira issue from within a test session, and have the issue automatically linked to the corresponding requirement.
• RY-266 Bugfix: In RY Reports, null cells would contain the previous value instead of being empty.
• RY-265 Ability to transform a table into requirements by selecting cells. It brings the flexibility that the RY macro can be created in the second column, or that the RY macro can reuse the contents of the cell if they already contain requirement numbers

• RY-239 The search query "isModified()" should include the modification of properties.

RY-245 Improve the performance when saving a page (creation or edit mode) and updating the text of requirements.

• Note: If you have a performance issue, please upgrade to Confluence 6.0.3 or above, since it is the first version that allows indexes on columns. Alternatively, you may manually create indexes (see page below).
• There is some technical information on this page: Performance for Requirement Yogi.

New features:

• RY-199 Onboarding: Display a notification to administrators to tell them the addon was installed (see details of notifications).
• RY-242 Display the count of requirements in the administration,
• RY-237 Better error messages in the Jira dialog when the user is not logged in, or when the applink between Jira and Confluence isn't fully set up,
• RY-235 Update logos,
• RY-209 Add another suggested filter, the root of the key.

Following RY-228, the dependency matrix became empty. This release fixes this major problem.

Also, several improvements for the new traceability matrix (RY-208):

• Add a link to insert the current matrix as a macro (at the top-right of the screen),
• Ability to display the current status of Jira issues,
• 3 options to display test results in the traceability matrix.

We've introduced a bug with the latest release: RY-234 - Reports display as empty.Also, fix RY-228 - Deleted requirements still appear in the coverage and dependency matrixes.

• RY-208 Multi-level traceability matrix
• RY-223 Fix a database error which sometimes appear when installing for the first time.
• RY-227 Some customers have created duplicate requirement keys by mistake. Merge them.
• RY-231 In the editor, display the space key when the suggested requirement belongs to another space.
• RY-230 Remove hyphen which appears by mistake in front of Jira issues.

RY-225: Fix the fact that test results were matched with the wrong requirement on most pages.After upgrading, please reindex the pages with a test results and a requirement, by clicking on the page's Tools menu (the 3 dots on the top-right) and choosing "Requirement Yogi".

• https://playsql.atlassian.net/browse/RY-224 Reorder the properties and links in the little detail dialog of the editor, so people can tick properties.
• https://playsql.atlassian.net/browse/RY-223 Fix error when installing the add-on from scratch.
• https://playsql.atlassian.net/browse/RY-219 Fix error when there are no suggestions on the search page.

The new API has a few user-facing features:

• It can re-synchronize with JIRA even if Confluence or JIRA were down during a change,
• It now always synchronizes immediately between JIRA and Confluence.

Important:

• Using the new API, all items are updated as soon as possible in JIRA.
• With the older version, one had to tick "Immediate synchronization" in the Confluence administration to get this behavior.
• As a consequence, the "Immediate synchronization" check-box is deprecated: Synchronization is always immediate. Please notify us if you miss it.

Other new features:

• RY-209 Add suggestions for filters.
• RY-207 Display an error message in the RY Report macro, when the sorting criteria is wrong.
• RY-205 Ability to display the requirement's text... inline.
• RY-204 Search across spaces is now possible.
• RY-154 Ability to export selected requirements (instead of all of them).
• RY-143 New API.

The administration page has changed, we've distributed the options into separate tabs to make it clearer, and added the "onboarding checklist".

• RY-200 Solve a small exception when ordering the RY Report macro,
• RY-199 Add an onboarding checklist,
• RY-191 Toggle the macro between "link" and "definition" of requirement.

• RY-190 Fix exception while renaming pages
• RY-189 Add criteria to build reports about tests.
• RY-188 Add contextual help when searching (Press Ctrl + Space).
• RY-194 Update the indexing algorithm to accept several test results per row (in preparation for a future release where we can actually manage them efficiently).

This version doesn't provide new features, except for customers who also use RY Testing & Compliance.

• RY-180 Preserve much more formatting, including the Status macro, in the excerpts of requirements.
• RY-130 Support for EasyDropDown
• RY-179 Javascript error in Internet Explorer (not Edge)
• RY-181 Support for the Scaffolding plugin
• RY-183 Fix bug about moving a page with requirement to another space.

I'd like to attract your attention on RY-172. A little caret is displayed for requirement links, which helps users distinguish links from original definitions. If this is a grave problem, please see the workaround in the issue.

• RY-172 Visual difference between requirements and links.
• RY-173 Inform the user when a requirement isn't showing the last revision.
• RY-174 Fix little bugs in the editor: Up and down arrows used to make the property panel disappear; the property panel would appear on the last Requirement macro instead of another.
• RY-169 Fix reports (for "@properties" columns).

• RY-168 Keep the size of images in requirements,
• RY-167 Performance problem with the suggestion mechanism,
• RY-166 Fix calculation of the coverage,
• RY-165 More formats for the RY Report macro,
• RY-144 Broken layout with some layouts.

• RY-157 Baselines: Tell the author how many pages will be frozen. This may help users to understand that not all pages of the space are duplicated.
• RY-163 Numbered lists <ol>: Keep the number in the excerpt, instead of replacing it with a dash.
• RY-155 If a user tries to create a requirement in a page by selecting the full text of the requirement, provide an explanatory error message.
• https://playsql.atlassian.net/browse/RY-150 Change the features that are disabled when a evaluation license is too old. The former behavior was to avoid saving new requirements, but this lead to discrepancies if modifications happened while a evaluation license had timed out. The new behavior is to not show the popup and the search results.
• And a little more explanations for REST resources, displayed in the REST API Browser.

• RY-122 Renaming requirements – Fix bug where some requirements wouldn't be renamed. Better messages for information after a renaming.
• RY-149 Return a message when using isModified() on a non-existing baseline.

• RY-122 Fix the renaming for instances with more than 500 pages with requirements. Check the user doesn't enter special characters.
• RY-148 Change the order of the requirement suggestions.

• RY-101 Ability to edit the Baseline blueprint,
• RY-116 Ability to suggest keys when there's not enough padding (e.g. going from REQ-999 to REQ-1000).
• RY-122 Wizard to rename requirements! Select one, several or all requirements in the search, click Actions -> Rename.
• RY-133 Add a message and debug information when requesting help from the support,
• RY-133 Ability to install Requirement Yogi without PSEA activated (the Excel exports),
• RY-134 Minor text change on baselines, for better explanations
• RY-136 Syntax issue when configuring the columns for the RY reports macro,
• RY-138 OAuth problem between Jira and Confluence: RY now displays the link to manage one's tokens.

• RY-132 Ability to use QuickSearch to find requirements
• RY-129 Don't collapse properties by default in the popup
• RY-127 Ability to update Blueprints
• RY-126 Ability to delete a requirement from the editor

Fix RY-116 for customers who store their data on MS SQL Server.

• RY-121 Immediate synchronization with Jira. There is an option in the administration panel.
• RY-119 Fix the bug where only the first Jira link was visible in the Excel export
• RY-118 Add the isModified('baseline 1') function, so people can search for modified requirements (since a baseline number or a baseline name).
• RY-117 A link to a wrong requirement version should ask which version the user wants to go to.
• RY-116 Fix suggesting a requirement number when there are more than 500 requirements in the space.
• RY-115 Allow ~ and @ in requirement's space keys, so users can use an email address as a personal space name.
• RY-114 Sort the RY Reports
• RY-106 Error opening the administration screen in Confluence 6.1
• RY-105 Only suggest requirements in the same space (see option in the administration).

• RY-83 Make keys case-insensitive
• RY-84 Collapse the excerpts in the popups, so users can see the links
• RY-108 Bug when creating a requirement through the little inline creation dialog, if the requirement had existed before.
• RY-110 Ability to suggest requirements based on other pages. We've also taken this opportunity to improve the caching, so creating links to requirements seems faster.
• RY-112 Remove the "Invalid Key" message which appeared when creating more than one requirement on a page, and suggest the next key that is unique across the space.
• RY-113 Update to new logos.

• RY-103 Error when displaying the administration panel for Requirement Yogi
• RY-100 Don't display deleted requirements (It causes more questions than solves problems)

This upgrade also upgrades PSEA from 1.0 to 1.2 (free and automatic).

RY-97 Bugfix for Confluence 6.0.1

RY-89 Compatibility issues with Oracle

• RY-81 The button to create another baseline from the index page doesn't work.
• RY-86 After the baseline, the Jira links should stay with the current version.
• RY-88 In Jira, add a button to synchronize all requirements.

• RY-82 Pasting a requirement URL in the editor should transform it into an RY macro.
• RY-79 The text of a requirement should not be blank while someone is editing it.
• RY-78 A specific situation where it's not possible to search by page when the only mention of a requirement is for a dependency.

https://playsql.atlassian.net/browse/RY-77 Error when exporting to Excel (happens when another user saves a requirement at the same time)

Major release! See the documentation: Dependency Matrix and Coverage.

• RY-58 Dependency Matrix
• RY-74 Excel exports with rich formatting (several sheets, dependency matrix, etc).
• RY-73 Maintenance: Avoid error when running the reports with no query.
• RY-76 Maintenance: Error in the web page after editing a requirement.

From this version, this add-on also contains the PSEA add-on. It's a module which enables exports to Excel with all Excel features (frozen panes or hyperlinks for example). It is mandatory. The only reason why it's separate is because it's a big library (Apache POI), so we didn't want to overload your Confluence installation and we share it with other Play SQL add-ons.

Major release! See the documentation: Dependency Matrix and Coverage.

• RY-58 Dependency Matrix
• RY-74 Excel exports with rich formatting (several sheets, dependency matrix, etc).
• RY-73 Maintenance: Avoid error when running the reports with no query.

From this version, this add-on also contains the PSEA add-on. It's a module which enables exports to Excel with all Excel features (frozen panes or hyperlinks for example). It is mandatory. The only reason why it's separate is because it's a big library (Apache POI), so we didn't want to overload your Confluence installation and we share it with other Play SQL add-ons.

Major release! See the documentation: Dependency Matrix and Coverage.

• RY-58 Dependency Matrix
• RY-74 Excel exports with rich formatting (several sheets, dependency matrix, etc).
• RY-73 Maintenance: Avoid error when running the reports with no query.

• RY-70 Don't require a link between the Confluence space and the Jira project. Just an Applink is enough, or non if there is no Jira.
• RY-72 Some table headers were ignored when they were incorrectly formatted or when the dynamic sorting modified the table.

• RY-64 Filter Jira issues by type
• RY-32 Baselines - Read the release notes.

Requires Java 8.

RY-66 Add a delay when displaying the inline popup.

RY-65 Compatibility with MS SQL Server

• In the report macro, style requirements with their color and font.
• RY-65 Support MS SQL-style quotes for table names ("[quoted name]").
• RY-69 Add a diagnostics screen, for customers who have problems with database vendors.

Important: Please check that you can search for requirements after installing this version. If the search fails, don't worry:

• Please report the bug to us,
• Uninstall this version,
• Reinstall version 1.4.2.
• Double-check which version is installed.

Atlassian's libraries are designed to offer the same quality for all databases, but we sometimes meet issues with other databases than Postgres, hence the feedback requested.

Fixed in this version:

• https://playsql.atlassian.net/browse/RY-62 Search should be case-insensitive.
• https://playsql.atlassian.net/browse/RY-59 Formatting of requirements in reports.

• RY-61 Image and links are now accepted in requirements !
• RY-56 Colors for requirements weren't set automatically.
• RY-56 In the inline creation pop-up, the list of requirement types was not updated until the cache was flushed.
• RY-56 Let the user define a Regex pattern to replace similar occurrences.
• RY-56 Properties should be ignored when building a suggested title for a requirement.
• RY-56 In the 'Requirement Yogi info' of a page, suggest to fix all places in the space where a key is used.
• RY-47 Fix Jira synchronization when the requirement was in a personal space.
• RY-50 Fix Jira synchronization when the issue was moved.

See the release notes: Keyword Dictionaries, Blueprints and Inline Creation

• RY-53 Blueprints to help getting started,
• RY-52 Move the dialog when hover over another requirement,
• RY-48 Inline requirement creation and dictionaries.

Note: The next version will require Confluence 5.9.x.

• RY-51 Can't replace a requirement.
• RY-49 Unique anchor for each instance of the same requirement in the same page.
• RY-46 New lines in requirement text and properties.

Blockers:

• RY-44 Requirement Yogi interferes with Confluence Questions. It is now fixed.

Minor:

• RY-42 Ignore all properties in a document, if your requirements are in tables. Ignore tables which aren't formatted with the headers on the top.
• RY-43 Allow Jira project keys to contain numbers.
• RY-45 Set the default page size in search to 2000 requirements, because it displays in a reasonable time. Also add a "limit" field in the RY Report macro.

Announcement: The price of Requirement Yogi will increase in March 2016 to 15% of Confluence. See the announcement.

• RY-35 Fix for empty queries in MS SQL,
• RY-36 Reject invalid characters for requirement keys,
• RY-37 Warn when the user copy-pastes a requirement instead of making a link,
• RY-38 Provide a way to capture and download server-side logs,
• RY-40 Fix failure when properties are longer than 255 characters.

There may have been an upgrade task failure with 1.3 for some customers. This version fixes the upgrade task and re-executes it.

See RY-33 for more details.

Includes all improvements of Requirement Yogi 1.3.0:

• Better synchronization with Jira. Ability to move requirements to another space. Fix broken links using the tools menu on the page. See this section for more information.
• Add properties for requirements. See Properties.
• Build reports and insert them into pages. See Reports.
• Advanced search queries - See Search Syntax (PostgreSQL users only).
• Create multiple requirements with a single keystroke.
• In the search, use single quotes instead of double quotes.

See resolved issues: https://playsql.atlassian.net/issues/?filter=10400

Note: Please upgrade to 1.3.1 rather than this version. Thank you.

• Better synchronization with Jira. Ability to move requirements to another space. Fix broken links using the tools menu on the page. See this section for more information.
• Add properties for requirements. See Properties.
• Build reports and insert them into pages. See Reports.
• Advanced search queries - See Search Syntax (PostgreSQL users only).
• Create multiple requirements with a single keystroke.
• In the search, use single quotes instead of double quotes.

See resolved issues: https://playsql.atlassian.net/issues/?filter=10400

• https://playsql.atlassian.net/browse/RY-24 Confluence Questions
• https://playsql.atlassian.net/browse/RY-23 Russian, Farsi, Tamul, etc.
• Support for Confluence 5.9.

To enable the Jira integration:

• Please install the Requirement Yogi connector for Jira,
• Please follow the instructions to install and configure Applinks.

• RY-12 Export to PDF/Word: Put full link of requirement
• RY-14 Real search (see syntax)
• RY-15 Export all requirements when clicking Export To Excel (It was previously limited to the current page of requirements)

Tracked as RY-7

When Requirement Yogi is used in tables, it concatenates all cells using " - " and uses it as the description of the requirement.

The former behavior was to use the longest cell of a table as the description of the requirement. It appeared some users need some information in all cells and this mechanism was error-prone (empty or short descriptions, anomalously long cells, etc.).

See RY-6: Non-administrators couldn't set the requirement description (which remained "undefined"). Fixed.

• RY-2 Fix the Delete button
• RY-3 Make suggestions clickable
• RY-5 Anonymous user should be able to insert references to requirements

• Requirements can now be inserted and searched when the database is MySQL.
• Anonymous users can now see requirement previews (provided they have permissions on the space).
• The excerpt is now visible for every requirement (It used to be that only links would display the original requirement, but it is more intuitive to display it in all situations).

Fixed an issue of version 1.0 with ActiveObjects and PostgreSQL.

• Requirement macro,
• Search screen,
• Links between requirements and pages,
• Excerpt on hover