I have added a backup issuetype, which is automatically being take care of by an external backup scripts. It adds a backup task, which another server is able to understand, and update it depending on it's progress, closes it when done. It also assigns it to me or someone if problems came up. Not that we would have many of those "API users", it seems they need real jira user permission to use the API - so they also need licenses. Can we somehow work around this if we want to keep individual users? The reason is that we have many of these api users, which we can not combine to one single user - as it's at the client side.
thanks for your quick answer. Problem is, that I do not want to have that single user across clients at their place including an open password. So they could potentially access other clients data... So the custom field itself is not enough.
It's like users not being part of the Jira group, they can email into the system, no problem. I'd wish this is the same for the API. Any chance?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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