Nic Brough -Adaptavist- Expert

I'd suggest you deal with the overwhelming email flow first, rather than try to wedge in something that interrupts people into a system that doesn't have a function for it.

You cannot search for things that are not there. The best you can do is look in admin to get a list of all projects, then look at a list of all projects with an issue count (write a filter for all open issues and use it in a filter statistics gadget, grouping by project, to get a list of projects that have issues), and…

Also bear in mind that the database only holds log in information for initial log in, via the UI and only when you're using a non-SSO solution.

No, because it's not as simple as "change workflow". You need to go through the migration process when you change a workflow, and Atlassian have not yet coded a REST call that can demand all the migration information up-front.

Do not do this. You will not be able to upgrade unless you change the code such that it knows how to account for your column, and you will need to make significant changes to the core code in order to use the column. As you go to investigate that, you'll find the code to do it is nowhere near as simple as you are guessing…

>But I could not find a space to create an issue through Jira software. Is there a solution to this problem? You click "create" I don't think you have explained the problem well, unless you really do mean you have not seen the create option in the menu, boards, backlogs and the portal. Could you explain the problem in more…

Why does it take two hours to write an issue?

No, there's no extra configuration, you just need to get the email into the inbox you have specified.

No, Jira's architecture does not support this. I'd recommend using the user's preferred notification route - set up an email send or Slack/Teams/whatever notification

Not a chance, you will need to upgrade the 2,7 to 3.something, then 4.something, then 5.something. 5.something can produce an export that 7 can read.y

I'd assume you have created an issue to log it against. What do you mean by "category"?

Cloud throws up a site that is broken up by application within it. When I visit https://aclsandbox.atlassian.net I get redirected to the conflluence behind it, which is on https://aclsandbox.atlassian.net/wiki and if I click through to its Jira, https://aclsandbox.atlassian.net/jira (and so-on for other apps) You do not…

The only way to do this from a short url is to visit the page and read it for the name. Technically you could work it out by de-encoding the eaY1Ag, but that would mean reverse-engineering the algorithm used to generate it, which is a LOT more complicated than just poking Confluence with a script or browser.

No, I have not touched it.

Go to https://my.atlassian.com , log in, cllick on Licences (if it's not already taken you to the list of products you already have), find the application you want the source for, and expand that line with the down-angle on the left. The expanded area will include a link to "download source" Note this only works for full…

I think you have landed in the wrong place in this conversation. Not because you have misread or misunderstood anything. This conversation looks, at a glance, relevant to "project type". But it is old. 8 years old. The meaning of "Project type" changed radically in October 2015, and this conversation really has no…

The last time I worked with SAP and Jira together, SAP had just made it a bit easier to set up "when X happens, kick another server by posting something to a url" actions, which meant it finally became able to avoid coding beyond worrking out what REST API to hit in Jira in order to create or update an issue. This was…

I think the problem is that the swimlane function needs information from issues that you have excluded from the board. Server does much the same, and there's a huge pile of errors in the logs when I try to render a board with an excluded Epic. Cloud is not the same software, but it is based on Server and it would not…

Ok, there's absolutely nothing wrong on the Jira side of your settings. So I am afraid it is the proxy setup. It sounds like it is doing half the job, in that it is passing https://my.company.com requests back to the Jira server, but I do not think it is returning everything it should in the other direction. It's taking…

I don't, not any more. It used to matter when we had Jira 4 and lower versions of 5, but even then, having a wide gap in the release dates didn't do too much harm - systems would talk to each other, but with one recent release and one ancient one, you'd just see a reduced function set, not a total failure. Nowadays, I…

Off-the-shelf, it's simple - to read a page directly, you need to be able to see it. If you're happy to work with copies (which you'll need to think about how to keep in line), then yes, you can have a private source and a more open replica. Things like the Comala apps can help you with that sort of approach (and they can…

Yep, the docs are now broken! 

Without knowing what your proxy is, the best we can do is confirm what you have set up on the Jira side should work. * Is your "base url" set to the address the proxy presents to the clients? (This one should not break your login, but would cause other issues, so it's worth knowing if you do have it to hand) * What,…

Sounds odd, given the docs, but try dropping the "" around "software". The other thing to try is letting the autocorrect do the work for you - go to the advanced search and belt in "projectType = ", then start typing softw... it should start making suggestions, including software, which you can then select and let Jira do…

Ah, hang on, no. There are two things Jira might be looking at when asking the question "is it open?". Neither of them are the status (directly) Jira Software mostly considers an issue "done" when it is in the last column on the board (columns represent status, so it is looking at status indirectly. But you can put any…

Yes, loads. Mostly app related, and all found during the test runs. You absolutely must go through at least two steps of upgrade - 6.4 -> 7.0 -> target, and I suspect your test runs will tell you that 6.4 -> 7.0 -> 7.13 -> 8.5 -> 8.14 is the least problem-prone route. 

Portals for customers, support channels, queues, service level agreements, all the reporting on all of those things. If you don't need a help desk system, you won't miss any of those things.

I am not aware of any partners or Atlassian offering apprenticeships. I'd check them out for entry-level positions though, after getting trained or certified here, it counts

Yes, the tick box you mention actually equates to having a workflow post-function that sets a resolution. So an issue has to go through the transition to get the resolution set by it. It's not a function of the status or column.

There's no way I can think to do that, other than a web-fragment that starts the move process for the issue.