We would like to upgrade our instance of Jira from server installation to cloud.
We are, however, concerned about a custom plug-in we have developed to our 'server instance' of Jira. This plug-in is about showing an extra drop-down field when creating an issue. It allows users to select from a list of values that come from another system. Behind the scenes, an HTTP request is made to one of our internal systems which returns a list of values to Jira and displayed to the end user.
To make this work we have done the following:
1. developed 2 .jar files (that hold code) and one .vm file (that hold UI elements).
2. copied one of the jar files to this location: \jira-home\plugins\installed-plugins
3. copied the other jar file to this location: \jira\atlassian-jira\WEB-INF\lib
4. copied the .vm file to this location: \jira\atlassian-jira\WEB-INF\classes\templates\plugins\fields\edit
5. from the admin panel ('Plugins' -> 'Manage Addons') we enabled the custom plugin
6. from admin panel ( Issues -> Fields -> Custom Fields) we enabled the field on various screens.
To summarize we have 2 questions:
1. Is it still possible to have such a custom field in Jira cloud installation? if yes, how? if not, what are the alternatives?
2. Can the method '/rest/api/2/worklog/updated' (from Jira API) return the value set on such a custom field?
You can't install Server add-ons on Cloud. In fact, you've not even written a proper add-on there, you've written a "type 2" and a "type 1" (which you should not do) and then hacked core code (which is even worse). Even if Atlassian were accepting new Server add-ons for Cloud (they're not), there is no way this one would make it in.
You'll need to re-do this as a Connect add-on if you want to add it to Cloud, OR come up with a way to do it properly that fits within the functionality Cloud provides. If you could describe what this add-on does for your end-users, we might be able to help you with that, or give you more focussed Connect guidance.
To do it as a Connect add-on, have a look at https://developer.atlassian.com/static/connect/docs/beta/modules/jira/issue-field.html and yes, you'll be able to use the REST interface to fetch it, although "fetch a worklog" is nonsense as they apply to issues, not fields.
Thank you Nic!
The scenario is work log synchronization with one of our internal systems.
The add-on we wrote sends a project id to the internal system and receives back a list of tasks defined for that project. This way, when we asks for work logs (currently using the Tempo plugin), the 'Task ID' travels along with the data and we know where to book those hours in the internal system. (You can imagine that the domain model we have in the internal system is different than the one in JIRA and therefore there is no notion of issues but rather tasks. Many JIRA issues can be associated with one task)
I also asked about the REST API since the Tempo plugin does not have this functionality (servlet API) in its cloud version. So actually I would expect the '/rest/api/2/worklog/updated' endpoint to return a list of work logs with their associated issues so that i can fetch the 'Task ID' from it.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs