Nic Brough -Adaptavist- Expert

I think we'd have made them by now, if there were.

The usual culprit for this one is a proxy that does not support web-sockets. Can you confirm whether you are using a proxy or not? If there is no proxy, then the next most likely cause is that your network is not allowing access to Synchrony. You mention your firewall having opened 8091 and 9443 - are those the ports you…

Ok, that log is riddled with SQL errors. You're using the embedded h2 database for this server, which has probably been corrupted. This database is susceptible to sudden catastrophic failure with no notice. Atlassian embed it in systems to get people started - temporary development or test systems, play areas, demos etc,…

What are you trying to update in Jira?

You will need to write a new app for Jira, one that can hide options from the users. I would question why you want to do this though. Why can't you trust your users not to convert items when they shouldn't?

No, the image is of the classic "swimlane" equivalent in Next-gen. Nothing has changed in those recently.

Repeating that you want something is not going to get you a different answer. There's nothing that will do this with your test issue types.

Not directly. There are some functions which can let you send email, but they're not going to be related to mentions. If you're moving to Jira Service Desk though, are you taking full advantage of the "customer" functions? That are accounts you can talk to. You can't mention them, but then there's no need to -…

I'm sorry "still appears in issues" makes no sense. Issues do not appear in issues, they appear in reports, search results, boards, backlogs etc. Can you tell me what you are looking at that is (presumably) a list of issues that your issues have dissappeared from?

No, there's nothing that will do that. But you don't really need a parent-child for this, a link with a clear name is all you need.

Issue type is not a custom field, it's a system field, and a structural one. I would say Jack is right - for some reason, someone in your organisation has added an issue type called "job story". You'll need to ask them what it's for (and as it's lead to you questioning it, I'd recommend having a conversation about why…

We can't begin to help if we don't know what the errors you are getting are. The error you are seeing might tell you something, but for most "it won't serve" errors, it is usually not able to tell you enough, and even if you gave it to us, it's very likely that the next reply will be: Is Jira actually running at all? What…

What do you mean by "disappear from project"? An issue will not spontaneously move to another project, so I'm not clear on what you are seeing. What are you looking at specifically? What thing that should be showing the issues is no longer showing them? (e.g. the issue navigator, one of the project views, a backlog etc)

> if SSMS can connect and be happy, what's up with the Jira installation? Probably nothing. Jira fails to connect messages are thrown when it tries to talk to the database and gets a failed response. If it were a problem in the Jira code or setup, you'd be getting crash messages, not "the database isn't talking to me" You…

There's no setting for this. The ordering of pages within the tree is free-form and you could have any one of thousands of desired default ordering patterns. Most people wouldn't want alphabetic. Some find "order that they're added" useful. If you coded for a default scheme, you'd need to code a way to support all the…

I do not think Atlassian are going to do anything soon to fix this reporting problem, which is mildly annoying. I don't mind that I have to copy and paste a short script into most systems, but it would be nice to not to have to (and not have to worry if the customer has one of the apps that can do it). Another option is to…

I hesitate to call it a "bug", as a bug is software doing something unexpected and wrong. This behaviour is not unexpected and there's some argument about it being "wrong". My opinion is not quite that it is "wrong", but very much "it's very unhelpful and confusing, and there's no good reason not to change the way it…

On the Atlassian side, see https://www.atlassian.com/trust/security/security-practices#business-continuity-and-disaster-recovery On the subscriber's side, there is an "export everything" function built into the Cloud services which you could use regularly to get a copy of everything. It's more intended for migration and…

I was heading for the logs next, so it's great that you are way ahead of me! Unfortunately, that's a deeply buried problem, and I don't recognise it and I can't place where it's coming from. I think this needs to go to Atlassian support over at https://support.atlassian.com/contact 

Watchers can decide to add or remove themselves from an issue, whatever their other permissions are. The CC field is less flexible, you'd need edit rights to select people for it. I suspect it's a custom field someone has added though, possibly because they are not aware of watchers, which they should be using instead!

No, Jira has not changed its key system, and its not going to, for the reasons above. Your numbering scheme does not do anything to add towards "parent can't be completeted until sub-tasks done" - Jira already handles that in the workflow and reporting with the simple numbering scheme. Recognising a subtask is also easy -…

What page are you looking at?

Could be either. Also might be in Australia or Singapore, and more regions are planned. See https://www.atlassian.com/trust/reliability/infrastructure By default, cloud will use the location nearest to your main activity, so if most of your users are in London, it'll probably land in the Republic of Ireland, if France or…

The communication between admins is paramount. I usually create an Atlassian Admin project with issue types reflecting what people might need from admins. Doesn't need to be a low level list, typically I've used issue types like "Make J/C/Bb do this", "something isn't working", "(new) project", "app request" etc. Then you…

You will need to use Atlassian Access in order to use an AD with Cloud.

To mention someone, they have to have an account in Jira - the system has to be aware of them. It doesn't matter how they get the account, via Core, JSM or Software.

Edit every transition in your workflow. * The All -> Done needs to have one (but not both) of these:* a screen that has the resolution on it * a post-function that sets the resolution to something (use the "update field" post-function, selecting resolution and the value you want to use for it - fixed or done are probably…

Go to each project and for each one, go into "customers" under "channels and people". At the top of the screen, there's a "change permissions" link which will allow you to change who can use the portal

Mentions can only work if the account is known to Jira as a user. So yes, you'll have to licence people to use the system if they are going to, well, use it (even if it's only for a mention)

Atlassian still serve an archive of all the older versions of Jira back to version 3.0 (and if you dig a bit, you can find older) - click on the "older versions" link in the download page. I'd strongly recommend reading the release notes, and for each version you choose to go through, check the supported databases and…