Nic Brough -Adaptavist- Expert

If you don't know who your admins are, ask the people around you who are using it, the person who gave you access to it originally, or the people who asked you to use it - many of them are likely to know of at least one person with admin access.

I think the idea came from people who wanted to watch pages for changes. You can adjust the notifications by not watching changes. I don't have the link for the request to ignore mentions, sorry.

Not ready yet, otherwise it would have gone out. You will need to tell your people that you made a mistake when you promised something you were not able to deliver. Hopefully Ryan will be able to give us an update here soon.

That looks like a backup run. Have you got the regular export to xml as a backup enabled? If it is, is that your only backup? If you do have another backup (recommended) then turn this off and see if the SQL stops being executed.

"GC Allocation Failure" can be summarised down to "I've run out of working space in the memory". It's more complex than that, but it is a good enough description for now - the system needs to be allocated more memory. These two lines in startup output are where I'd look: Maximum Allowable Memory : 981MB Total Memory :…

So that has nothing to do with events or workflow properties. Your workflow is built to only let you move from the current status through "resolve issue". It either has no transitions from the current status to others except the "resolve issue" transition, or if it does have others, they have conditions on them that are…

There are some apps in the marketplace that can help you by listing and sorting custom fields by name or type, but that's only helping, not actually doing the work of finding duplicates. Identifying duplicate fields is a manual task, a human, one with understanding of the reasons people may be adding fields or the…

I would recommend getting in touch with an Atlassian partner - see https://partnerdirectory.atlassian.com for help finding one that suits you best.

Scriptrunner does not have a way to provide entire new field types in Jira. You'll need to find or write a field that can handle multiple text boxes, or simply add the text fields you need separately.

Team-managed projects do not use schemes for their configurations, they have local internal and non-shared configurations. You'll need to add your issue types inside the project configuration, by hand.

Be aware that if you go this way, you will be creating an ugly user experience and you'll probably need apps to provide the validators.

Cloud has "Automation" built into it, but if you find that can't do everything you need, then look to Scriptrunner, Powerscripts, Jira Suite Utilities or Jira Misc Workflow extensions.

You do not. If someone can create an issue in a project, then they can create an issue of any type.

A combination of the examples at https://library.adaptavist.com/entity/identify-the-groups-of-a-user and https://library.adaptavist.com/entity/remove-specified-users-from-a-group (tweaked from "delete" to "add") should do the job.

I'm afraid that's something to do with the software on your 'phone. It's working fine for the people near me who use Atlassian on the their iphones

You need to change the way you use the board. Map the "cancelled" status into the "done" column on the board. The act of cancelling them means they are done so tell Jira that they're done by moving them into the last column.

We don't know, we're not your administrators, we're a Community of people here to talk about Atlassian stuff, and have less knowledge of, or access to, your systems than you do.

It means what it says - you've given a git executable a path to a repository that is not responding. What error do you get if you run the command it says is erroring on the command line?

Only the standard Epic issue type can be used as an Epic in Jira. You can rename Epic if you want, but you can't ask other issue types to work as Epics If you do rename it, bear in mind it's just the issue type name that changes. Stuff like the Epic report, Epic Status, Epic link and so-on will all remain named as Epic…

The way to roll back an upgrade is to restore the database backup you took before applying the upgrade, then point the old installation at it. 

Yes, then you'll need to get your people to use the new portal if they wish to raise that type of request.

Ok, I think you'll need to talk to your file share admins/experts to find out why it is not writing particular file types quickly enough. The fact you've changed the type of file share from one to another (albeit similar) and this problem jumped out then is screaming that it's the file system. But we needed to check the…

You've got something in your testing routines or reporting that is sending Jira or, more accurately, the Zephyr app you have installed on Jira, a duff date, or there's broken data in your database, with a date being misrepresented somewhere. (The fact it gives you a valid looking date suggests the former possibility, as a…

That suggests something damaging the file as it is being uploaded or going to the file system. Have you tested disabling any anti-virus on the file share (on all the computers sharing it)?

We can't answer that question, you have not explained what SIPRnet is which rules out a lot of us from answering (I happen to know, and yes you can do it with DC, but you can't assume most of the audience here might know what your obscure acronym might be)

By the time enough of Atlassian's customers decided they wanted one (most still do not - checkbox custom fields and/or sub-tasks are more useful for most), there were already some third-party apps available that could provide them. So Atlassian went and did other things, rather than implement something that would kill off…

It cannot work this way. A request is part of a portal. A portal belongs to a single project (a 1:1 relationshio). So any request you raise in a portal has to belong to that portal, which, in turn, means the issue behind the request must belong to the project that provides the portal.

Why would they? (I mean, I know what you're thinking, but it's not clear to most from your question. I'd prefer you to explain in your own words, you will get a better answer if you do)

Ok, the next step is a look at the logs on the Jira server. When you get that red warning about a failure, something with more detail will have been written into <Jira home>/logs/atlassian-Jira.log I can't begin to guess what that might be, I've seen several root causes come out in there for various reasons why a disk…

Boards do not belong to, or contain, projects. They select for a set of issues to work with on the board. So, to create your board, start by running a search like "Project in (ABC, DEF, GHI)", save it as a filter, and then create a board from that filter.