JiraServiceContextImpl breaks backwards compatibility

XMLWordPrintable

    • 4.03

      Hi,

      I'm trying to upgrade my plugin (Tempo) to JIRA 4.3. We are using JiraServiceContextImpl when we create or update worklogs as in this example:

      tmpWorklog = worklogService.updateWithNewRemainingEstimate(jiraServiceContext, worklogResultNewEst, true);
      

      The problem is that you have removed the JiraServiceContextImpl constructor that takes com.opensymphony.user.User as parameter and you have thus broken the backwards compatibility.

      You have changed a lot of the API to take both the OSUser and the new Crowd user as you describe here: http://confluence.atlassian.com/display/JIRA/Plugin+Developer+Notes+for+JIRA+4.3 but can you please make JiraServiceContextImpl backwards compatible as well?

      I noticed that you say that you changed some "Non-API" classes to use only the Crowd user. Is the WorklogService considered "Non-API"? If so, which interface should we use to register and update worklogs?

      Best regards,

      -Bjarni

              Assignee:
              Peter Leschev
              Reporter:
              Bjarni Thorbjornsson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: