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

JIRA 4.0 Enterprise Requirements

XMLWordPrintable

    • 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.

      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.

            [JRASERVER-11125] JIRA 4.0 Enterprise Requirements

            Frank Stiller added a comment - - edited

            Can we reopen this issue? I guess the Confluence Page: http://confluence.atlassian.com/display/JIRACOM/JIRA+Enterprise+Requirements is less used than this JIRA Issue, is it?

            My problem with the Wiki Page is, you cant see what issues have been resolved and dependencies/links are relatively static, in JIRA you can link more smoothly.

            Frank Stiller added a comment - - edited Can we reopen this issue? I guess the Confluence Page: http://confluence.atlassian.com/display/JIRACOM/JIRA+Enterprise+Requirements is less used than this JIRA Issue, is it? My problem with the Wiki Page is, you cant see what issues have been resolved and dependencies/links are relatively static, in JIRA you can link more smoothly.

            Z Craven added a comment -

            We also considered WAN Disco but when you consider you have to buy extra JIRA licences too the cost was just too much.

            I think JRA-9 (Timezones not handled properly) should be added to this list, though my suspicion is that will never be done unless JIRA is one day rewritten from scratch.

            Z Craven added a comment - We also considered WAN Disco but when you consider you have to buy extra JIRA licences too the cost was just too much. I think JRA-9 (Timezones not handled properly) should be added to this list, though my suspicion is that will never be done unless JIRA is one day rewritten from scratch.

            Sam Gaw added a comment -

            Clustering is a big deal, having a single point of failure is not an enterprise feature. Nor is having to buy additional OEM products so I don't consider WANDisco a viable option.

            Sam Gaw added a comment - Clustering is a big deal, having a single point of failure is not an enterprise feature. Nor is having to buy additional OEM products so I don't consider WANDisco a viable option.

            Tom Miller added a comment -

            I would like to see JRA-13362 linked in. Now that Greenhopper is available, not having a way to manage critical path is a show stopper from a PM point of view. I also would like to see some sort of security enhancement on hiding Time related elements from our end users.

            Tom Miller added a comment - I would like to see JRA-13362 linked in. Now that Greenhopper is available, not having a way to manage critical path is a show stopper from a PM point of view. I also would like to see some sort of security enhancement on hiding Time related elements from our end users.

            Tom Miller added a comment -

            After reading several threads on the issue of User Support, it seems that the easy answer is a dual configuration scheme. I would go for three, but basically if you turn off a feature in Admin, no one sees it. So if you had 3 user classes: End User, Collaborator, Internal User; and configured the rendering engine for each person per project, that would solve the problem. Not perfectly, but it get us most of the way there and the technology is already in place. A simple case statement before you parse the HTML for the page is all you would need.

            Tom Miller added a comment - After reading several threads on the issue of User Support, it seems that the easy answer is a dual configuration scheme. I would go for three, but basically if you turn off a feature in Admin, no one sees it. So if you had 3 user classes: End User, Collaborator, Internal User; and configured the rendering engine for each person per project, that would solve the problem. Not perfectly, but it get us most of the way there and the technology is already in place. A simple case statement before you parse the HTML for the page is all you would need.

            Frank Stiller added a comment -

            i dont see the advantage between a link list in confluence and in jira.

            For tracking purposes i even find the jira list better. The votes are still done in jira, and in confluence there isnt any added content, is it?

            it's just for my understanding

            Frank Stiller added a comment - i dont see the advantage between a link list in confluence and in jira. For tracking purposes i even find the jira list better. The votes are still done in jira, and in confluence there isnt any added content, is it? it's just for my understanding

            AntonA added a comment -

            Jeff,

            Good idea.

            I have created:
            http://confluence.atlassian.com/display/JIRACOM/JIRA+4.0+Enterprise+Requirements

            Thanks,
            Anton

            AntonA added a comment - Jeff, Good idea. I have created: http://confluence.atlassian.com/display/JIRACOM/JIRA+4.0+Enterprise+Requirements Thanks, Anton

            Jeff Heinen added a comment -

            The one thing I liked about this was the collection of links and issues that I otherwise did not know about. How about if someone made a confluence page these items? That was people can still share and comment about issues, and all of the voting is done on a per-issue basis.

            Jeff Heinen added a comment - The one thing I liked about this was the collection of links and issues that I otherwise did not know about. How about if someone made a confluence page these items? That was people can still share and comment about issues, and all of the voting is done on a per-issue basis.

            AntonA added a comment -

            Hi,

            I would like to thank everyone for their comments and input. We can see that this issue is a good "hub" for recording the features you believe are important for enterprise deployments.

            This issue, however, does not help us prioritise between features that you believe are important. Due to the number of issues mentioned here,and the complexity of some of them, we will not be able to implement them all at once. Quite a few JIRA customers are voting for this issue, and while the popularity of the whole list goes up, it does not help us organise the issues in order of importance.

            Due to this reason, we would like to resolve this issue, and ask you to vote for the actual individual features that are important to you. This will greatly help us to prioritise them.

            Thank you for your help and understanding.

            AntonA added a comment - Hi, I would like to thank everyone for their comments and input. We can see that this issue is a good "hub" for recording the features you believe are important for enterprise deployments. This issue, however, does not help us prioritise between features that you believe are important. Due to the number of issues mentioned here,and the complexity of some of them, we will not be able to implement them all at once. Quite a few JIRA customers are voting for this issue, and while the popularity of the whole list goes up, it does not help us organise the issues in order of importance. Due to this reason, we would like to resolve this issue, and ask you to vote for the actual individual features that are important to you. This will greatly help us to prioritise them. Thank you for your help and understanding.

            Ivan Kulchytskyi added a comment - - edited

            Please attach JRA-6057
            JRA-1604
            JRA-1397
            JRA-3774

            Ivan Kulchytskyi added a comment - - edited Please attach JRA-6057 JRA-1604 JRA-1397 JRA-3774

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

                Created:
                Updated:
                Resolved: