Our models are going to be really simple.
This is how my board looks like in Jira, issues can only move forward and they can only move from one column to the next one, you cannot skip any columns. We (Jira) don’t recommend this method (Basic auth) unless you are building tools for internal use only, like scripts and bots. We are also going to use Basic auth for simplicity and because our goal is to learn how to integrate 3rd party tools rather than how to do proper authentication in Jira.We will be using Jira Cloud platform API v3.You don’t have any compulsory fields to fill before moving an issue (like logging time, etc), otherwise your UI will require extra fields for the user to enter them.The Jira issue ID will based on our current git branch, so our plugin will take the issue ID from the branch we are on rather than forcing the user to type it or having to select it from other place. What we want to do is being able to move an issue on a Jira scrum board to the next column without leaving Android Studio. Today we will integrate Jira in our plugin. I will apply a simple MVP pattern that you can then follow or change to MVC or whatever you feel comfortable with. The goal for today’s article is to explain how you can integrate third party APIs and libraries into your plugin. Remember that you can find all the code for this series on GitHub and you can also see the relevant code for each article on its own branch, this article’s code is in the branch Part4.
0 kommentar(er)
