App own configuration ‘Use ISO Week’ is added, as it is not possible for the app to access corresponding Jira Look And Feel setting (see https://ecosystem.atlassian.net/browse/ACJIRA-882).
It is available on User Default Settings tab of the app configuration, or as User Preference:
It is now possible to sum up number issue fields by several Parent Issue Type. Please find setting at Issue Hierarchy tab in Configuration page.
Old single Type remains valid.
Please note, it is valid for Jira Portfolio issue hierarchy.
It is now possible to log work for users (yourself or other users if allowed, for Timesheet Reports and Gadgets only) in table in case of Group By Field: Worked User. See Log Work link in worklog details popup, when clicked on issue level:
When clicked on user level with no work logged yet, Log Work Done dialog is opened immediately. When clicked on issue level, work can be logged with simplified popup.
Please see also Log Work for Others (for Timesheet Reports and Gadgets only).
The backend implementation for emails bodies for Timesheet Reports and Gadgets for Cloud was changed. Design of emails could be different but content remain same.
It is now possible to restrict logging work on certain issues via app.
For this, there in app Configuration at ‘User Default Settings’ tab admin should set ‘In Progress Issues jql’ query and check 'Do not allow to Log Work on other issues’ checkbox.
It will not be possible to Log Work Done on Issues not matching the query.
Please note, default Timesheet report will show all issues matching the query, when logging work via '+' in Timesheet or app Log Work dialog is available.
Please note, users can rewrite JQL in User Preferences for themselves. For instance, developers need query like 'assignee = currentUser()', but SD engineers prefer 'status = "In Progress"'.
Please note, it is still possible to log work for any issue via Jira standard Log Work Done dialog, with default Jira Provided Time Tracking Provider or using Jira mobile application.