Imnew to Atlassian Developing and for a Project we have to develop a plug in that connects to the JIRA Database.
Im at a loss after scouring the Internet, I cannot seem to find a fitting solution.
Can you give me some ideas which classes to use in the JIRA rest API?
First, we need to know what type of coding you are doing. The options are broadly:
I'm guessing you mean 2 or 3, but they make a bit less sense if we don't explain the full range.
Also, don't say "database" - you don't want to code for access to the database, it's not sane. Always go through the APIs.
Do what? You haven't explained what your add-on is going to do. You've just said "connect to the database" which is, quite simply, the wrong way to approach doing things in JIRA.
Could you describe what your add-on is aiming to do, in terms of what the users might see or get?
The goal is to connect to the db, pull two numbers out, and create the sum and average value of these two numbers and then export the results to txt and pdf.
My job in this is only to realize the db connection to access the numbers.
This Project is part of a group project in which we are practicing Scrum, and creating a plugin for Jira.
These numbers are just dummy variables. The goal is to program a plugin that gathers information from the JIRA db about issues, progress, etc. and enable the user to generate reports.
My job is to implement the link between the report generation and the JIRA db.
How could I realize this with the API? All examples I found so far do not work because the imports cannot be resolved.
If your imports aren't resolving, then the code is broken (although I know getting the imports right are a pain when writing add-ons for Atlassian stuff). It's worth going into a bit more detail I think.
Also, you probably need to define the questions you're looking to answer.
If you really want totally open-ended reporting, then I'd lean toward moving to a database tool instead of trying to read the JIRA database in the application. It's not built for reporting, but it can be used, especially if you use a product that understands the JIRA database would be best. (I tend to avoid open-ended reporting - it usually leads to users coming to you to "explain why this report tells me X" and you spend hours working out that their reporting was built by the clueless and it's nonsense!)
If you want this reporting inside JIRA though, then definitely need to fix your imports! Even if you weren't working with the API much, you'll still have problems.
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
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