Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Connecting to JIRA via a JDBC Driver Edited

I can "Export Issues" via the UI without any issues, but I am attempting to connect to JIRA using the CData JDBC driver.

Testing the Connection Fails:

jdbc:jira:User=john.doe@company.com;Password=***********;Url=https://company.atlassian.net;

Error: You are not authorized for this operation

I need to access via JDBC to the same data produced by the Jira.csv file, when select “Export Excel CSV (All Fields)”, I suspect that this data resides in the jiradb.jiraissue table.

Is this a permissions issue?

Thanks

1 answer

0 votes

Not permissions, just the connection.

I'm glad to say Cloud does not allow any direct access to the database behind Jira.  You'll have to do whatever you're trying to do with sane methods of access - UI or the REST API

Do you know if there are any tools available that perform the "Export Issues" --> “Export Excel CSV (All Fields)” as a scheduled automated task to deposit the Jira.csv file on the filesystem?

It is possible with Scriptrunner on a Server install of Jira. 

Apology/Disclaimer: I work for Adaptavist, so, of course, it's part of my job to sell Scriptrunner. 

There may be other tools that can do this in the marketplace, but I do not know if there are.  Because I've got SR "on tap", I have not needed to look. 

I do know there are tools that can produce far better exports than the Jira native stuff that SR would just call.  I don't know if they could be automated this way.

Without other tools, SR could be used to build a filter, run through all the issues it returns and belt out a csv file, but I do not think this is a good solution.

However, that is very vague.  What problem are you trying to solve by having regular exports to CSV?  There's a good chance we could suggest a better solution, if we knew what the underlying problem or reporting hole is?

Preparing a demo for a client, who would like to automate the step in jira that exports tickets in csv/excel format to a file locally, all of the remaining steps are managed by Nifi, I'll look into your product.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,105 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you