3.5.0


Administration	REQ-4775	New Feature	The project specific permission settings for R4J no allow permissions for the folder structure. If users have the Create/Modify Issues permission, they can create new or add existing issues to the tree. If users have the Create/Modify Folders permission, they can create new folders or move folders to others. If users have the Delete Issues permission, they can delete issues. If users have the Delete Folders permission, they can delete folders that do not contain issues. If users have the Delete Folders and the Delete Issues permission, they can delete folders that contain issues. If users have the Move Issues permission, they can move issues in the tree. If users have the Move Folders permission, they can move folders that do not contain issues in the tree. If users have the Move Folders and the Move Issues permission, they can move folders that contain issues in the tree. Definiton: "Folders that contain issues" mean folders that have issues as either direct children or in one of their sub-folders.
Administration	REQ-4884 REQ-4247	New Feature	Project Categories can now be defined in the add-on administration. All projects that are created with any of the selected project categories will be enabled for R4J automatically.
JQL	REQ-5023	New Feature	New optional parameter for requirementsPath and requirementsFolder JQL functions allows to restrict result set to issues that have a link of a specifc type. Example issue in requirementsPath("My Project/Folder 1", "relates to")
Coverage View	REQ-5001 REQ-4157	New Feature	The first row of the coverage view can now be filtered to limit the displayed issues to a specific folder of the requirement tree.
R4J Issue Detail View	REQ-4890	Improvement	Edit mode changed from wiki mode to visual mode
	REQ-5521	Bugfix	Fixed missing expand/collapse icon in R4J issue detail view
	REQ-5543	Bugfix	Reading Panel "Click to add a child requirement" unclickable
	REQ-5485	Bugfix	Clicking "Click to add a child requirement" text does not display Add Child Requirement dialog
	REQ-5358	Bugfix	Requirements pane throws "Request failed"
REST API	REQ-5289	New Feature	You can now define the property "Fields to Display" as parameter in the REST API call "CreateCoverageView"
	REQ-5531	Improvement	Project keys and issue keys are no longer case sensitive in REST API functions
	REQ-5030 REQ-5031	New Feature	New REST API endpoint to query tree structure of folder com.easesolutions.jira.plugins.requirements/1.0/tree/<projectkey>/foldertree/<folderid> Folder ID for root folders is -1. Example GET https://jira.example.com/rest/com.easesolutions.jira.plugins.requirements/1.0/tree/ABC/foldertree/123
	REQ-5002	Improvement	REST API endpoints updated for suspect configuration. See here for more details.
Template Export	REQ-5131	Improvement	Table creation is now properly supported in Word Template Export
	REQ-5413	Bugfix	component variable not properly rendered on JQL tag of word export template
	REQ-5473	Bugfix	affectedVersion filter caused erroneous output
Suspect Report	REQ-4272	Bugfix	Suspect Report browser back button not works
Suspect Report	REQ-4271	Bugfix	Suspect View sorting order lost after clear
Reuse	REQ-4976	Bugfix	Issue Links are considered in Reuse which were not selected in configuration
Xray Compatibility	REQ-5151	Bugfix	create links for multiple existing issues should update xray req status
	REQ-5168	Bugfix	deleting issue links should also update xray req status field
	REQ-5169	Bugfix	updating issue links should also update xray req status field
	REQ-4921	Bugfix	Usage of Link functionality in R4J does not trigger XRAY Requirement Status - Test
	REQ-4685	Bugfix	Problems with Xray Test Cases creation in R4J Tree or Coverage View
	REQ-5349	Bugfix	Problems with Xray Test Cases creation in R4J Tree and Coverage View
Zephyr Compatibility	REQ-5248	Bugfix	Wrong value shown for Zephyr field in detail view
Zephyr Compatibility	REQ-5047	Bugfix	Reuse: Unable to reuse Zephyr Test Case due to API error