Archived (implemented) feature requests
- Better Tempo context support (start date - end date, user, etc.) - DONE
- Optionally verify merge commits - DONE!
- Show the actual commit message in commit message based rejection messages - DONE!
- Support for nFeed - DONE
- Improved integration with Bitbucket Server (formerly known as Stash) - DONE!
- Support for Confluence Data Center (i.e. Archiving Plugin in a cluster) - DONE!
- Provide a way to check if issues mentioned in commit message are assigned to the committer - DONE
- Excel export security: enabling (and disabling) Excel exports based on roles, groups, projects, issue types, etc. - DONE!
- Support for the Insight (Asset Management) custom fields - DONE
- Better Tempo context support (start date - end date, user, etc.) - DONE
- Support for GitHub - DONE
- Support for Bitbucket (cloud) - DONE!
- Support for the Issue Statistics gadget - DONE
- Multiple supervisors - DONE
- Excel exports directly from the Tempo views - DONE!
- As a user, I want to use clear action links (ex: "Archive") instead of page labels in the web UI and in the notification emails - DONE
- Verifying the commit policy at commit time (in developer forks) - DONE!
- Support for the nFeed plugin's custom field types - DONE
- Should support resizing rows only or columns only (DONE!)
- Support for the Agile Sprint Burndown gadget - DONE
- Support for the Time to SLA plugin's custom field types - DONE
- PDF export directly from a Tempo timesheet - DONE!
- Export the full issue change history to Excel (DONE!)
- Support for the JIRA Agile Rapid View gadget (Scrum and Kanban boards) - DONE
- Post-function scripts should allow uploading the PDF document as an issue attachment - DONE
- Sending Excel reports in scheduled emails - DONE
- Visibility of the usernames in content status info should be configurable (for privacy reasons) - DONE!
- Sending Excel reports at workflow transitions or issue updates - DONE
- Automatically accept any commit (at merges) that was previously accepted - DONE!
- Initialize page view dates at the plugin's first installation date or treat "unknown view date" in a smarter way - DONE