Comments
-
Ok, that suggests that while Confluence might be set up for an SSL connection to the database, Synchrony is not, so it's throwing errors. But, I think that's a red-herring, as you still have the problem when not using Synchrony. I'd want to check the atlassian-confluence log to see what is going wrong on edits
-
The ranking is not as simple as 1,2,3... it's a relative thing called "lexorank", and the data in it does not make a lot of sense to humans.
-
Try order by Rank That should sort out the filter. Then try the "board" drop-down and look for configure board
-
No, but sort of. A board is not a container of issues, it selects a set of them. There is no "move between boards" because they do not contain the issues. What you need to do is adjust the boards filters so they only show the issues you want on each board. If you do it carefully, you can make it so a card appears to move…
-
Admin -> custom fields -> configure.
-
If the rank field exists and is locked, then all you need to do is use "order by rank" in your board filter.
-
Yes, because you're editing them.
-
People have used Jira to do all sorts of things, including tracking financials.
-
I don't think I understand your question, but if you edit an option, you change it. That's what the edit is for.
-
Admin -> custom fields -> configure. The field in your picture is a "cascading select"
-
Yes, you can edit them. You may break saved filters that use the options, but your users will be told what is wrong and will be able to edit them to fix them
-
Its in plain Jira, not the service desk.
-
Search for the issues with the issue search, then use one of the export options in the issue navigator.
-
That suggests that you've told Jira to use the users and groups from AD in read only mode. You'll need to add the users to the groups in AD
-
I'm afraid the flag is a global one, not configurable by project.
-
Start wirth https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html and https://confluence.atlassian.com/adminjiraserver/installing-jira-data-center-938846870.html
-
Ok, it's not Cloud. So you can edit them. I guess you're just looking in the wrong place.
-
There is no scripting in native Jira, you'll need to get one of the add-ons that provides it. I'd look at Automation and ScriptRunner (and yes, I work for Adaptavist, so there's a bit of bias when I recommend SR)
-
That's correct, the accounts do not belong to you, they belong to the user.
-
It is whatever you set for them if you're creating the account locally, or what they set if they're logging a new account for the first time, or whatever the directory setup sets if you're using external user directories.
-
Run a filter for "project = X", then look at the export options in the menu.
-
The calls in the docs are given with curl as the example because it's simple, widely available and easy to translate into other formats. Have a look in the jhipster docs to see how it makes calls out to other systems, you should be able to drop the body of the curl calls straight into it.
-
You'll need to raise it with Atlassian over at support.atlassian.com/contact
-
Assuming you mean for an issue, you'll need to join jiraissue to an AO table for the sprint, look at the links table and another jiraissue row and then AO table for the epic name. Teamlet could be anything, so we can't tell you where to look for that, unless you can explain what it is in your Jira. Whatever you're doing…
-
That suggests the person trying to end the sprint does not have the permission to modify the sprint in one or more of the projects the board covers. Check the board filter to see what projects it includes, and change the user's permission to match (remember that there don't have to be any issues from a project in the…
-
Ah, I see. I thought you were talking about user accounts and teams, but it's the site name. Someone has already used tryvin as their site id, and then let it lapse. Atlassian don't let people re-use old site names automatically. Yuo will need to get in touch with support to see if they can re-enable that name (they may…
-
I'm afraid we don't know. It sounds like this is something that has been set up on your Jira, not an off-the-shelf one, and it's specific to your system, which we, as end-users of Atlassian software, have no access to.
-
You'll need to use the existing account, you can't create duplicates.
-
There are two routes, but they are similar. Backup Jira to XML, or get a database dump and a copy of the attachments. * Install the new operating system * Install a clean empty Jira on it, get it working, then stop it. * Restore the xml or the database
-
What app are you using for test cases?