Nic Brough -Adaptavist- Expert

You will need to go through all the permissions, removing whatever it is that allows these people access to the projects you don't want them to see (you'll probably need to replace it with something that still lets in the people who should see it)

It's the path on the left, in yellow. You need to define a second "field configuration" where affects version is set mandatory, and then tell the "field configuration scheme" for the project to use the new "field configuration" when the issue type is Bug.

You can not. Administrators, by definition, should be able to administrate the system, and permissions are one part of that.

That looks like it means Confluence is using the system Java install, and that version is fine. But the error message is telling us that it is getting invalid parameters. Confluence is not setting anything wrong according to the results of your search. Have a look through…

In theory, all you have to do is create a new jira, started up looking at an empty database so that it goes through the standard initial installation, shut it down, repoint it at the old database and restart it. But, that will only work if you were using the internal directory for users. If you were not, you'll need to…

The last line of the error is not helpful. You need to read the log for the root cause error, not the information about the action taken as a result.

You'll need to read the logs to see what the connection error is.

Go to your list of licences, and expand the one for Bitbucket. One of the things you'll see there is a licence key. Copy that, then log into your Bitbucket and go to the licence section under admin, and paste the key into the area for licence keys.

This looks like it is a problem with the connection to the user directory system you are using. You should start by looking at the logs at the time people are trying to log in. れは、使用しているユーザーディレクトリシステムへの接続に問題があるようです。あなたが人々がログインしようとしている時にログを見ることから始めるべきです

This should give you most of what you need: https://library.adaptavist.com/entity/update-a-field-across-all-the-linked-issues-itsm

You'll need to look at the logs to find out what is going on. Ideally, just tail the application and security logs while someone tries to log in.

This line is the problem: def optionsFound = optionsManager.getOptions (optionsFieldConfig) It's going off to the field definition to get the list of possible options. You really need to be reading the data from the issue, not the custom field definition. That means something like def customFieldValue =…

The only thing I've seen that does that is https://almworks.com/jiraclient/overview.html (Although I know a lot of people who have scripted automations for the same reason)

You will need to describe the problem in a lot more detail if you want our help. "It doesn't work sometimes" is not enough to work with.

Yes. I know a lot of places that work with Confluence "off the shelf" and are highly effective and productive with it. With most of your complaints about macros, you'll find that there are good reasons that they don't support functions you've named - it's when they don't have any real use for doing it. (And as for the last…

You will need to renew the license. We can't help you with this, we can't see your licence details and you've not given us any real error report to work with. Best guess is that your "local ip" can't reach Atlassian's licence servers, but you'll need to debug that on your network.

This will happen when the account does not exist, or the user directory for the system is not reachable or responding.

Ok, we're going to need to see screenshots of the board, board settings and the issues that it is reporting as "being in an error state"

They don't have "respective sprints" A board shows you issues as defined by its selection criteria. The data it shows will include all relevant data, including sprints that issues have been added to.

There is no way to migrate the ranking and hence sprint data cleanly without apps (and most of the migration apps don't do it well either)

Ok. Core does not have any of the hierarchy functions of Epics. Your Epic issue type here is just another Task with a different name. But more to the point here - no, the project boards quite simply show the whole project, there's no limiting them by issue tpe or other data.

Are you using just Jira Core or do you have Jira Software? (Not worried about Jira Service Desk, just if you have Software or not)

You don't create issues on boards, they are not containers, they are a view of a selection of issues (in projects - those are issue containers) The reason you see the same issue in two boards is that the filters for each board selects for that issue. If you want two boards to select different issues, you'll need to change…

All of your different closed status? And are all your sub-tasks showing in the last column?

No, you don't need extra logic. I should have explained the last bit a bit more (albeit 8 years ago). Jira has a custom field with a type of "group picker". If you have one of those, and you select a group in an issue, you can tell the notification scheme "on event, notify the people represented by the data in a custom…

I'm not sure how else to say "the last column on the board". Literally, look at the board, it has several columns, what is the last one? (Ok, one quirk, you need to be reading left to right)

There's not a lot more we can tell you - edit the workflow, adding the transitions you need to make "edit" happen in the workflow, and set them up with conditions that limit them to the people who should be allowed to edit the field, and a screen that has the field on it.

Seriously, reading the database is the worst possible way to get information from Jira. Could you explain why you are trying to do this? We can probably give you a far better way to achieve your goals.

You will need Atlassian Access for that (assuming by "integrate", you mean "use Active Directory for our user list and authentication)

Start with https://confluence.atlassian.com/adminjiracloud/configuring-workflow-schemes-776636598.html Note that you don't "see a workflow" in a sprint, you see issues, which follow their assigned workflows, as defined by the project.