This page lists major improvements and feature requests that can help with Enterprise Deployments of JIRA. If you would like to share your thoughts please add comments to this issue.
JRA-1560 - Better support for logical operation (and/or/not) type of filters
JRA-1330 - Field level security permissions
JRA-1397 - Assign issues to multiple users or a group
JRA-1604 - Import / Export (backup / restore) individual projects
JRA-12241 - Support for Product Suites / Sub-Projects
JRA-8663 - Ability to share components between projects
JRA-1072 - Shareable subprojects
JRA-11541 - Ability to hide/show issue tab panels
JRA-3156 - Required: Project Group Administrator
JRA-6896 - Add ability to create sub-task via soap
JRA-2134 - jira-admin "login as" a given user
JRA-2509 - Save, reuse and share Dashboards (like dashboard picklist)
JRA-2764 - "Issue Type" Security
JRA-7990 - Restrict sub-tasks by issue type
JRA-3821 - Priorities, Resolutions and Statuses per project / issue type
JRA-6381 - Permissions per workflow step / state
JRA-846 - Support for subcomponents
JRA-6057 - Online users
JRA-10042 - Add an improvement to workflow to allow multiple users to approve an issue in any order
JRA-5865 - Allow permission schemes to be configured per issue type
JRA-7909 - Search/ filter for "empty" fields
JRA-2411 - Ability to edit and remove work logs
JRA-9306 - Work Log: number of hours per day must be project-specific setting, NOT global
JRA-5509 - Reporter Group permission
JRA-5783 - Make field required only for one state transition
JRA-3774 - User Management: Disable user accounts
JRA-2735 - Propogate actions/transitions to linked issues
JRA-3619 - Validate email addresses of users who sign up
JRA-8689 - Turn off dashboard customisability for different groups and/or different dashboards
JRA-5276 - Allow default issue security level at user/users-group level
JRA-9107 - Create post-function to set security leve
JRA-4618 - When reporter differs from creator, the creator should be recorded in change history
JRA-1962 - Migrate to Atlassian User (externalised LDAP management)
JRA-1369 - Notifcation improvements to reduce volume of email sent by JIRA
JRA-1560 - Better support for logical operation (and/or/not) type of filters
JRA-1391 - Renaming groups after creation
JRA-1549- Ability to rename a user Minor Open
JRA-1100 - Ability to Edit Comments
JRA-2367 - Separate "delete attachment" permission
Comments (2)
May 19
Andy Brook says:
Inbound email handling in 3.12.x is unusable in my environment owing to users no...Inbound email handling in 3.12.x is unusable in my environment owing to users not logging in with their (long) email as the ID and complications in being able to determine a 'short' userid from a given email address (different domains, different structure of email address). See JRA-14973 for details.
May 20
Neeraj Jhanji says:
What about including JRA-6146 - Implementing issue locking in JIRA 4.0 or 4.1?What about including
JRA-6146 - Implementing issue locking
in JIRA 4.0 or 4.1?