FIX Fixed the issue where “apply-template“ does not work when it is added in a conditional statement.

EASE-22220, EASE-22118, EASE-22252, EASE-22271, EASE-22268, EASE-22267

IMPROVED Rendering and editing features are now aligned with the detail view editing capabilities of Jira, enhancing the overall user experience and functionality.

Some notable improvements and fixes added in easeReq detail view:

1. Users can now inline edit description even with images inside.

2. Users can now add/edit tables.

3. Users can now add/edit Date format.

4. Users can now see the correct data numbering in the rendered description. Previously, if numbering started at 2, the easeReq detail view displayed 1.

EASE-16948, EASE-17705, EASE-17725, EASE-18005, EASE-18539, EASE-18599, EASE-19139, EASE-19388, EASE-20540, EASE-21749, EASE-21950, EASE-21950, EASE-22040, EASE-22042, EASE-22168,

IMPROVED Added the following performance improvements.

1. Reduced calls to Jira for issue details when using linkedissues in the template.
   For example, an export of 1,000 issues with 1 linked issue each.

   1. Previous implementation: 1 Jira call to retrieve parent issue information, followed by another call for linked issue information.
      --> This required 2,000 Jira calls. Assuming each call takes 1 second, the export process would take approximately 33 minutes.

   2. New implementation: Combined both calls (for parent issue and linked issue information) into one.
      --> This reduces the total to 1,000 Jira calls, so the export process would take approximately 16 minutes.

2. Reduced calls to Jira for revision details when using “revisions” in the template.
   For example, an export of 1,000 issues with each issue having less than 1000 revisions.

   1. Previous implementation: 1 Jira call to retrieve parent issue information, followed by another call for the revision information.
      --> This required 2,000 Jira calls. Assuming each call takes 1 second, the export process would take approximately 33 minutes.

   2. New implementation: only 1 Jira call per parent issue is needed.
      --> This reduces the total to 1,000 Jira calls, so the export process would take approximately 16 minutes.

3. Reduced the details requested for each Jira issue to only what is required in the export template.

4. Removed unnecessary processing of wiki format since Jira cloud already supports rendered format.

EASE-21166, EASE-21473

FIX Resolved an issue where the levelheading statement fails to generate a heading level in the Word document when the exported tree contains only folders.

EASE-22020

IMPROVED Enhanced rate limiting management effectively mitigates the occurrence of 429 errors from Atlassian for API calls from easeRequirements to Jira. It is important to note that this implementation could impact application performance when usage nears the established rate limit.

To learn more about Jira´s rate limit, refer to Rate Limiting in Jira Cloud

EASE-21055, EASE-21027, EASE-22039, EASE-21919,

FIX Fixed the issue where “linkedissues“ context does not return the description of the linked issue.

EASE-22118

IMPROVED Reuse operation now defaults to “Unassigned“ if value of assignee in the source issue not assignable in the target project.

EASE-21729

FIX Fixed the issue where incorrect data is exported in the word document.

EASE-21968