Comments
-
:-) Tempting, as I probably don't want to live here after Brexit.
-
I would try reducing both to 768Kb as the article suggests, but do it in steps of 256Kb or 512Kb and monitor it carefully to see how the pattern of problems changes. However, changing the memory settings might not be the right thing to do. It might improve it in terms of impact, and it could make it worse, but I doubt it…
-
Another thing we discussed was the use of "articles" rather than questions. Some vendors are writing some rather good guides on setting up their add-ons to deal with various ways to use them to enhance products. I'm finding myself reading all of these and then linking to them instead of answers.
-
Yes, it's the same procedure.
-
Could you give us a screen shot? (Please obscure part, but not all, of the email address in there to avoid spam - e.g. if it's Nagesh.Subrahmanyam@somewhere.com, cover the omewhe bit)
-
There's no explicit way to do this as suggested, but there are (not quite ideal) ways to get there. Go to a dashboard you own (I usually create a new one for "housekeeping"), and add a "issue statistics" gadget with the following settings (you can accept the defaults for the ones I don't name) * Project/filter: your filter…
-
You've given it an invalid email address. It can't proceed without a valid email (and you'll need a valid one to create accounts and get important information). Check for invalid characters and extraneous spaces.
-
I'm afraid not. An Epic is not considered to be a strong container of issues, just an ad-hoc grouping. You can delete the Epic, and it won't touch the issues, except for removing their Epic Link. What you'll need to do is run a search for "epic link = <your epic>", use bulk edit to remove all the issues, then delete the…
-
This does generate some work for partners - as a test or demo Cloud system is used by a company, then they realise it's not suitable, they ask us to help migrate them to server. Either their own hosted one, or by one of us that does managed services. It's not the main driver of Cloud to Server migrations, but it's not…
-
When you complete a sprint, all the issues you have not finished are, by definition, not done with, so they need to go either into another sprint, or back into your backlog. They still need action, so you need to keep them somewhere that shows them as needing work. Only issues that are in the far right-hand column of your…
-
Use the built in "backup and download". It gives you a full backup in a format ready to be loaded into another Jira system which you can just drop into a NAS with a script. You can run it every 48 hours. You can find a script to automate it at…
-
I don't think that is caused by indexing. If it were, then the project/full indexing that Cloud does automatically will be fixing it.
-
You would need an add-on to do this. I think there was one in the marketplace. Problem is that it's of little value. The Jira keys are unique and far more functional than a separate request ID. I think the question to ask is "Do your users really need another key?" The downsides are that they'd have to manually search for…
-
The answer I gave there was written before I'd seen an email handler go haywire, exactly as Andy says. That's reason number 5, but also the primary culprit in the cases I've seen since then!
-
You can't create product categories, that's up to the admins and moderators. The community is still not sure how we want to be doing this, although we do have "help vendors identify stuff they can help with" very high on the to-do list. @Monique vdB- any advice?
-
Same here, I'm told Privacy Shield won't be enough. We need the option to host inside the EU. The Beta in Europe is in Ireland, so that would solve it, if I understand correctly. But only if Atlassian will guarantee that if you ask for EU data, it will only be held and processed in the Irish centre.
-
Same answer. You need to be a board admin of a board with a simplified workflow, or you need to be a Jira Admin and edit the workflow.
-
Personally, I'm an advocate of throwing away the "resolution says whether it's ended or not" (it should remain as the "why"), and building a relative meta-status function instead. The problem with what you've got is that there's no clear open/closed decision, whereas at least the current "resolved = ended" function is…
-
That's just the installation. You have not converted anything yet. Go back to your old h2 installation, and back it up using the xml export. Import the resulting file into the new postgres based installation
-
It does sound like a GC problem, so enabling logs would be good. 3,000 issues doesn't need 3Gb RAM for the most part, so having it too high might be leading to long garbage collections. Increasing RAM if it is a GC error might just reduce frequency but increase their length. You'll want to get to the bottom of what the…
-
Ah, ok. That's going to be a problem even if you upgrade - they're probably going to have issues doing the upgrade with an unknown error in place. You really need them to give you the logs so you can work out what this is.
-
I think you are stuck with Connect - the field module really does only support those types of field.
-
Have a look at https://www.atlassian.com/partners/search - you may want to search locally, or for experts in the right field. Atlassian will support you if you buy Cloud and try to migrate, but it will be at the point at which it goes wrong and you get stuck. As Mikael says, a partner could help you more, be with you on…
-
<sigh> I am a customer, not an Atlassian. I'm definitely being grumpy about it, but that's because others here are not grasping that it really is simple. There are complexities (took me a while to get my head around roles), and the defaults are poor, but "add user to project" could not get more simple without losing the…
-
Sorry, yes, it could be AV killing the download part way through as well.
-
Which migration guide are you reading? (There are several!) Even without them, I think you're mostly going in the right direction, but I would strongly recommend upgrading a copy of the 6.4.11 database to 7.0 and then take that to 7.5. A large jump in numbers can mean more headaches, but there's also code removed from 7.2…
-
Good choice, they're nice people :-)
-
It's not that complex. * Check the rules for project access - hopefully, you've stayed with the default ones that say "browse project = role: user" * Add your user to the "can use application" group so they can log in. * Add them to the role of user in the project you want them to see. The bit people do struggle with is…
-
No, because it's not a performance problem. Plus, as you're on Jira 7.1, you're using Java 8 already. Is there a reason you are not reading the logs? Please?
-
We're not ignoring feedback, the problem is people not understanding that it is not that complex, and the defaults are to be open and collaborative.