Nic Brough -Adaptavist- Expert

Go into the board settings and add JQL to the quick filters.

No, it is designed not to allow this.

XSLT is not a "format", it is a way to read or style XML. If you're going to use XSLT to read or present Jira data, you will want to export the data to XML.

Could you check the mapping of status on the board? As you say they disappear when the status changes, it sounds like the new status is not mapped into a column on the board, so they won't be displayed.

You're right, it's not helpful. It can't be. If Jira is working without a vpn, but fails when you are on a vpn, then the problem is with the vpn, not Jira. We can't help without more information on the source of the problem (the vpn, not Jira), and even if we did, we're Atlassian geeks, not vpn geeks.

This means that the connection between your client (browser) and server (Jira) is being interfered with or even blocked by something on the communication layer. If you find this happening when you connect to your VPN, then there is something wrong with the VPN. Is it ok if you connect to the VPN and then log in to Jira…

I'm afraid @Calvin Luc is right, the "standard" that Atlassian have moved to is not optional. Which is a shame as I don't like "markdown", and refuse to use it, on the grounds that its choice of markup for emphasis is completely counter-intuitive drivel.

Ok, I get "lighthouse analysis", but there's nothing on how the script runs, what triggers it, or what it updates outside Jira. However, at a guess, I'd say you want "stuff that script does runs as part of a transition in Jira"? There's a range of things you could do here. If your script is working perfectly, then, as an…

You can get roughly what you suggest, but there's a couple of things to understand first. A board is not a container for issues (projects are containers). A board selects issues to display. You can not * move issue from one board to another (you change an issue such that one board stops selecting it and another begins to)…

You will need to get in touch with the administrators of the wmg.atlassian.net Cloud system. Here, we are end-users of Atlassian software. There might be a "wmg" admin here who might see this and contact you, but most of us know less about that system than you do. If you do not know who your admins are, ask your colleagues…

There's a lot of work. I only see bits of it. In London, the sponsorship seems ok, as partners are happy to offer beer and pizza, but there is a constant search for venues and speakers. If I were to do it (which I can't, but even if I were allowed, I know I don't have the tenacity to keep on top of it all), I would start…

I hate to point out that you would have had a quicker answer from a search engine than us. See https://developer.atlassian.com/cloud/jira/service-desk/rest/

You can use the "field configuration" to hide the priority, which will also stop it taking any value on create/edit. But I think it's like resolution - once set, the priority will still appear whatever you do. (Not a bad thing for resolution, as that should never be hidden, at least until Atlassian move to a sane…

Hmm, you should be able to change the status name back exactly as @Petter Gonçalves says - admin -> issues -> status In the workflow view, edit the workflow, and in the graphical view, click on the status, which will then throw up a box where you can change it. If that's not working, could you explain what exactly is…

You can't do that in plain Jira - selecting an issue type in the pie chart explicitly tells Jira you want to report on issue types separately. You can do what you need if you use automation, scripting, or more powerful reporting that Jira's off-the-shelf (exactly as @Tom Harris - Old Street has suggested)

I think I know what you are getting at - you are seeing two different editors. This happens when your system is moved on to using the "new editing experience". All new pages use the new editor, but existing pages that were created with the old editor continue to use it. They are not spectacularly different, barring the…

An Epic sounds right - you can use it to connect separate pieces of work in different projects.

I think you might need to explain what this has to do with Atlassian software? (My guess is that you've followed a link for help, but you've found the link for help with the documentation system in use by the vendor, not help with the vendor's software)

Yes, if JspWiki can make appropriate calls to Jira over a REST interface, and exposes a remote interface for Jira to use.

Most of the resources for the SOAP API for Jira wound down a long time ago, but there are still some. https://developer.atlassian.com/server/jira/platform/creating-a-jira-soap-client-4227095/ may be a good start for you, as it's got authentication and Java to do it with! I would be remiss if I did not mention that you…

There is not enough context in your question, I am struggling to understand what you are saying. You say you have a "quick filter" for "Labels = Request". The JQL is clear and valid. As a quick filter, this will be restricting the board it is on to issues with that label (from the full set of issues selected by the board…

There is no way to do this in Confluence, it's a wiki, not a document storage solution, and as such, the product owners don't see it as needing any clever versioning schemes.

Sorry for the delay, bit behind at the moment. Yes, the doc you have found is for writing apps for Cloud, which should be able to do this. I mentioned "user macros" which Cloud users cannot write for themselves. I'm afraid I don't know about coding for Cloud like this, I've only ever written for Server Confluence and only…

This means that Jira thinks something else (probably another Jira) is locking the database open. Are you trying to run a second Jira against a single database? Or is your Jira already running? Can you completely stop all Jiras on the server, check the home directory for any files called "lock" and remove them, then restart…

Could one of your admins have set the export limit to 0? I know I've done that before, to get people to come talk to me about exporting (too much)

When you say you "can't see all the issues", could you be more precise? Is it all issues, or a subset? Where are you looking? Could you try editing one of the issues mentioned in the indexing log and see if that throws a similar error?

Jira is not a mail program, there's nothing like an "inbox" that we could use to do this. You should use filters (or possibly queues if you have service desk) to enable people to find the things they need to do.

I am afraid you are going to need to give us a lot more information. You have not said what is incorrect, what you are expecting, or what you are importing. We can't help you without more context.

This is not really the whole re-index failing, it is reporting a single error in one place (although it is happening to many issues). The rest of your issues are absolutely fine, and in fact the index for the failed issues is also correct. It has only failed for that one field on the issues. Are you sure field 11260 is the…

Yes, SR can be used to read a field and parse it. If your text is consistent, it should be quite easy to do. From memory import java.text.SimpleDateFormat import java.util.Date def oldDateField = customFieldManager.getCustomFieldObjects(issue).find { it.name == "My old date string field" } Date newDate = new…