Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-11125

JIRA 4.0 Enterprise Requirements

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      This issue is an open petition to Atlassian. We believe that JIRA is missing a number of features that prevent it from being truly enterprise-ready. We are not asking to have these issues addressed immediately, but we do believe that our maintenance agreement for JIRA enterprise entitles us to some consideration of how these issues fit into the JIRA roadmap.

      If you are an enterprise customer, please consider not only voting for this issue but also comment to indicate that you are signing this petition.

      Also feel free to link in other issues that I have been missed. Any issues that I link will meet the following criteria:

      1. Major functionality change, either an improvement or a new feature.
      2. Likely to be high priority for a customer of JIRA enterprise.
      3. Identified for quite some time (most over a year, often multiple years).
      4. Not scheduled for any version of JIRA.
      5. May have comments about bumping it back from release to release.
      6. Typically has a high number of votes and watchers.

      For more details on why I felt it necessary to create this issue, consider reading my <RANT> on JRA-1549.

      Attachments

        Issue Links

          incorporates

          Suggestion - JRASERVER-1560 Better support for logical operation (and/or/not) type of filters.

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-6896 Add ability to create sub-task via soap

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRASERVER-846 Support for subcomponents

          • Closed

          Suggestion - JRASERVER-1072 Shareable subprojects

          • Closed

          Suggestion - JRASERVER-1100 Ability to Edit Comments

          • Closed

          Suggestion - JRASERVER-1330 Provide field-level security permissions

          • Closed

          Suggestion - JRASERVER-1369 Reduce JIRA email chatiness

          • Closed

          Suggestion - JRASERVER-1397 Assign issues to multiple users or a group

          • Closed

          Suggestion - JRASERVER-1549 Ability to rename a user

          • Closed

          Suggestion - JRASERVER-1560 Better support for logical operation (and/or/not) type of filters.

          • Closed

          Suggestion - JRASERVER-1604 Import / Export (backup / restore) individual projects

          • Closed

          Suggestion - JRASERVER-1962 Improve the LDAP stack in JIRA

          • Closed

          Suggestion - JRASERVER-2134 jira-admin "login as" a given user

          • Closed

          Suggestion - JRASERVER-2367 Separate "delete attachment" permission

          • Closed

          Suggestion - JRASERVER-2411 Ability to edit and remove work logs

          • Closed

          Suggestion - JRASERVER-2509 Save, reuse and share Dashboards (like dashboard picklist)

          • Closed

          Suggestion - JRASERVER-2735 Propogate actions/transitions to linked issues

          • Closed

          Suggestion - JRASERVER-2764 "Issue Type" Security

          • Closed

          Suggestion - JRASERVER-3156 Add additional administrative privileges to users with Administer Projects permission

          • Closed

          Suggestion - JRASERVER-3774 User Management: Disable user accounts

          • Closed

          Suggestion - JRASERVER-3821 Priorities per Project and Resolutions per Issue Type

          • Closed

          Suggestion - JRASERVER-4618 When reporter differs from creator, the creator should be recorded in change history

          • Closed

          Suggestion - JRASERVER-5276 Allow default issue security level at user/users-group level

          • Closed

          Suggestion - JRASERVER-5783 Make field required only for one state transition

          • Closed

          Suggestion - JRASERVER-5865 Provide ability for permission schemes to be configured per issue type

          • Closed

          Suggestion - JRASERVER-6381 Permissions per workflow step / state

          • Closed

          Suggestion - JRASERVER-7330 Implement cluster support

          • Closed

          Suggestion - JRASERVER-7909 Search/ filter for "empty" fields

          • Closed

          Suggestion - JRASERVER-9306 Work Log: number of hours per day must be project-specific setting, NOT global

          • Closed

          Suggestion - JRASERVER-10042 Add an improvement to workflow to allow multiple users to approve an issue in any order

          • Closed

          Suggestion - JRASERVER-11541 Ability to hide/show issue tab panels

          • Closed

          Suggestion - JRASERVER-12241 Support for Product Suites / Sub-Projects

          • Closed

          Suggestion - JRASERVER-20550 Hotfix to 3.13 for subtasks

          • Closed

          Suggestion - JRASERVER-3619 Validate email addresses of users who sign up

          • Gathering Interest

          Suggestion - JRASERVER-5509 Reporter Group permission

          • Gathering Interest

          Suggestion - JRASERVER-8689 Turn off dashboard customisability for different groups and/or different dashboards

          • Gathering Interest

          Suggestion - JRASERVER-9107 Create post-function to set security level

          • Gathering Interest

          Suggestion - JRASERVER-65813 Make field required only for one state transition

          • Gathering Interest

          Suggestion - JRASERVER-72769 Provide the ability to rename groups after creation

          • Gathering Interest

          Suggestion - JRASERVER-1391 Provide the ability to rename groups after creation

          • Under Consideration

          Suggestion - JRASERVER-7990 Restrict sub-tasks by issue type

          • Not Being Considered

          Suggestion - JRASERVER-8663 Ability to share components between projects

          • Not Being Considered

          Activity

            People

              Unassigned Unassigned
              c0424e273244 Phil Haar
              Votes:
              66 Vote for this issue
              Watchers:
              62 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: