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

Feedback for Java API

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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      In JIRA v5.0 we are creating a separate API module for plugin developers to depend on to give more security that the plugin will remain compatible with future JIRA versions.

      Plugins devs can change the dependency on "atlassian-jira" to "jira-api" in their maven pom.xml like so:

              <dependency>
            <groupId>com.atlassian.jira</groupId>
            <artifactId>jira-api</artifactId>
            <version>${jira.version}</version>
            <scope>provided</scope>
        </dependency>

      This issue is intended to gather feedback on what is included and what isn't included, and is of particular interest for JIRA v5.0 Early Access releases (milestones and betas).

          Form Name

            [JRASERVER-25596] Feedback for Java API

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3059724 ] New: JAC Suggestion Workflow 3 [ 3688939 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2617330 ] New: JAC Suggestion Workflow [ 3059724 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2585945 ] New: Confluence Workflow - Public Facing v4 [ 2617330 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361913 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2585945 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2129543 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361913 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2092733 ] New: JIRA Bug Workflow w Kanban v6 [ 2129543 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 886363 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2092733 ]
            jonah (Inactive) made changes -
            Description Original: In JIRA v5.0 we are creating a separate API module for plugin developers to depend on to give more security that the plugin will remain compatible with future JIRA versions.

            Plugins devs can change the dependency on "atlassian-jira" to "jira-api" in their maven pom.xml like so:
            {code}
                    <dependency>
                        <groupId>com.atlassian.jira</groupId>
                        <artifactId>jira-api</artifactId>
                        <version>${jira.version}</version>
                        <scope>provided</scope>
                    </dependency>
            {code}

            This issue is intended to gather feedback on what is included and what isn't included, and is of particular interest for JIRA v5.0 Early Access releases (milestones and betas).             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-25596].
              {panel}

            In JIRA v5.0 we are creating a separate API module for plugin developers to depend on to give more security that the plugin will remain compatible with future JIRA versions.

            Plugins devs can change the dependency on "atlassian-jira" to "jira-api" in their maven pom.xml like so:
            {code}
                    <dependency>
                        <groupId>com.atlassian.jira</groupId>
                        <artifactId>jira-api</artifactId>
                        <version>${jira.version}</version>
                        <scope>provided</scope>
                    </dependency>
            {code}

            This issue is intended to gather feedback on what is included and what isn't included, and is of particular interest for JIRA v5.0 Early Access releases (milestones and betas).
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-25596 [ JRACLOUD-25596 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

              Unassigned Unassigned
              mlassau Mark Lassau (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: