Comments
-
There are several reasons to move to server. Some people have issues with the latency and network between them and Cloud, for some it's about the location of the data, for most of us, it's about the inability to scale and/or freedom to configure what we want. There is a very good chance that you will find it faster on a…
-
No, as Joe says, it's the "browse" permission in your permission schemes. Check what that says.
-
You've put the Jira admin group into the global permission for "can use JIRA". Go to global permissions and remove it.
-
You can use the instructions for upgrading a Linux install. Some directories are in different places, as Macs have a different disk layout, but nothing moves in an upgrade, so you probably won't run into that.
-
Ah, it was just the new interface. Sorry, completely misdiagnosed it!
-
It asks for a fix version because fix version lists are different between projects. You could configure your field so that it has two separate option lists, that would cause similar behaviour.
-
JIRA uses log4j for its logging, which can be set up to log to remote systems instead of a local file. I can't tell you if that would work for sentry-java though, I've not used it.
-
Code. Two options spring to mind - hacking the "move" functionality in the core of JIRA, and not actually doing it in the move at all. The second option means writing a listener that could catch the "move" event, have a look at the issue and change the number as appropriate (technically, this would happen after the move,…
-
Your licence entitles you to use any version released before the end date on the licence. So if you've paid through to 2020, you'll be able to go to 7.2, 7.3, 7.4, 7.others-not-out-yet, and probably 8 and 9 if they're released in the next 3 years.
-
Ah, you said JRJC, so I assumed you were looking for REST calls. Internally, most of the historical stuff can be got at via the ChangeHistoryManager. Probably the most obvious call is ChangeHistoryManager.getChangeHistories(issue)
-
Ahh, well spotted. I was going to ask about the processes you'd been through (including what you'd downloaded) next.
-
They are separate servers. So you'll need to *duplicate* your user accounts on both of them. Your AD already allows for that, but it sounds like you need to look at the access. You just need to look at the JIRA Software users to see what grants them access to JIRA Software (probably they are in a group like "JIRA software…
-
Your projects are configured differently. You'll need to re-configure the target project so that it supports the fields you are losing, or accept that the data will be lost. For the assignee data, you should temporarily include the source project users in the "assignable user" permission while the move is done, it should…
-
How are you drawing the fields into your add-on, and what type of add-on is it?
-
But the order does not matter. The only place you see the order is when you're an admin editing the workflow.
-
No, because the order of validators does not matter. Each validator is a simple yes or no question. If any one of them is a "no", the whole thing fails. Think of baking a cake - you have validators like "do we have eggs", "do we have flour", and "do we have sugar" and "do we have butter". If any of them are "no", the…
-
My squad have been doing a lot of Cloud imports recently and we've run into all sorts of different errors that hide behind that message. I'm afraid it could be any one of a number of things, and as you need the logs to start diagnosis but don't have access to them on Cloud, the short answer is "we can't even begin to…
-
Yes you do. JIRA Software can't run on it's own, it runs on top of Core. The JIRA Software download you've used to create your system is a bundle of Core and Software. The installer will have given you an error on the command line when you ran it and selected "upgrade", but also dumped some information into <jira…
-
The sprint data is on the issues.
-
You'll need to find or create a blueprint to do this.
-
Probably stack-overflow, it's got a lot of spectacularly bad and wrong advice on it.
-
What else from https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html have you tried?
-
Share with customer makes the comment visible to everyone who can see the issue/request. Internal comments do not appear on the requests, so a customer can not see them.
-
Pages inherit their view security from their parents. If a user can't see page 1 and 2, then they can't see the child pages under them. You'll need to open up 3's parent, or move it to a parent that the users can see. Edit rights are not inherited, you can give people the right to edit 3 without granting it for 1 or 2. (I…
-
An upgrade option won't appear for JIRA Core, as that is the structural thing that everything runs on top of, and has to be updated manually. If there is an upgrade for JIRA Software available that is compatible with your underlying Core installation, you'll find the option to upgrade in "manage applications" But for your…
-
The database is not built for reporting, so you're not going to have a good time trying to do this with SQL. The data is drawn from the issues and sprint data, so jiraissue, customfieldvalue and the AO tables related to Software are the starting point. But some of it is calculated and kept only in the index, and more…
-
Could you describe the symptoms? If you pick up a card and try to move it, what happens? Do the target columns light up and the card wanders back to its origin when you drop it, or do the columns not light up at all?
-
No. It should be owned by the Bitbucket user. It's fine to edit it as another user, but don't change the ownership.
-
Use the flag for the history /jira/rest/api/2/issue/<issue-id>?expand=changelog
-
Run a search for the issues you need to move Select "bulk edit" from the tools menu in the issue navigator (the results screen from the search) Select "move" from the list, and choose Project B as the target