Comments
-
Yes, start at https://developer.atlassian.com/cloud/jira/platform/rest/
-
No, you get no access to the database. You have to use the REST interface to get data.
-
Start by defining "problem"
-
Labels have NOT been removed, just the labels panel.
-
The "workaround" is simple - use JSD as intended. Create and use the linked issue so the developer has a separate issue to plan and track through their process.
-
That needs to be changed in the user management system you are using for Cloud. That's the google accounts, your SAML system or Atlassian ID (if the Atlassian ID, then the user owns the account and can change it over at id.atlassian.com)
-
You don't need to upgrade anything, it's already configured for it, and by default, it's sending mail already as well.
-
You will need to write a Connect app to do that.
-
Jira does not have any functions for following people. It is an issue tracker, people using it are only really ever going to be interested in issues.
-
To get the first screen, connect your Jira to an external user directory.
-
1) No. 2) The error message says Jira was installed to run under the user jira. Use the user jira, not jiraadmin
-
You don't. Cloud does not support any domain outside atlassian.net, so your url must be <something>.atlassian.net It also does not do direct edits, even within that domain. If you want to change to another <something>.atlassian.net, you need to buy the new Cloud system, export the current one and import it into the new one.
-
You will need to explain what you think IDP is
-
I'm afraid Behaviours are Server only, because of the limitations the Cloud Connect framework places on apps.
-
The "OD" in those numbers tells us that this is Cloud Jira, where the version does not matter to end users (as you have no control over it and it doesn't matter to add-ons beyond saying to vendors "this does not currently work with Cloud")
-
Upload a new icon in Admin -> Issues -> Priorities
-
What do you mean by "make a magnifying glass"?
-
I'm afraid there's no way to do this with post-functions. The closest you can get is to pre-load the question. Use two transitions that do the same thing, but have different conditions on them.
-
What do you mean by "integrate"? What are you doing and where, in which application? Stay away from the database, there be dragons (you'll be ok if you read them carefully, but any attempt to write will result in your data being charred to a crisp and noisily eaten)
-
It's the same answer - the workflow in your diagram is not the one in use for your project. As above, Status is a global list that all the workflows draw their status from. To avoid affecting other workflows, you need to use status that are not shared with them (although the effects are down to changing a status name…
-
Status icons are simple configurable images. If you don't like the colour of one, replace it with one with a colour you do like.
-
Business boards are very simple, they map each column as one status in your workflow. If you don't want issues to appear in the published column, you have two options 1. If the published column is the last column on the board, wait a fortnight and the issues will drop off 2. Don't put issues in the published status For…
-
Have another read of the answer. It's not about not using groups, it's about wasting your time using groups for permissions. A shorter way to put it though: Stop using groups (in permissions) and use roles.
-
Yes, this is a good use for Core!
-
My guess is that you are on Cloud, where you can not add SMTP servers, you have to use the Atlassian one pre-configured for their services.
-
The tree only appears when you are looking at the pages area (something that has annoyed a lot of users, as most of us want the page tree there all the time). are you in the right place?
-
I still don't think you've got it. Jira does support that. You're not looking at it right. Please, go read the accepted answer again
-
Assuming you mean you want to use the system "original estimate" related fields, then all you'll need to do is identify the create and edit screens for the tasks and add the field "time tracking" to them.
-
Actually, both of those are very minor points, especially in a tool that is explicitly built for collaboration.
-
You can make separate REST calls to update Jira, including the ability to create versions (options in custom fields were not there last time I looked)