Comments
-
Could you explain what this has to do with Atlassian? Proview is not one of their products, or an app in the marketplace
-
What errors are you getting? What does the log file say the problem is? If you've followed the documentation, the most likely problem is that you've edited server.xml and miskeyed something that has broken it so that Tomcat can't make sense of the file and hence stops when it tries to read it.
-
Jira doesn't record that, it can't because of the nature of the field. Imagine this sequence: * Fire up a browser and go create an issue with a multi-user picker. * Put in Charlie * Put in Bob * Put in Alice * Remove Charlie from the list * Click create The important thing here is that the browser is not sending any data…
-
It depends on what backups you took - an xml backup can be restored directly into a new empty system, or a database/file-system one can be restored over the top of a working empty Jira.
-
Have a read of https://confluence.atlassian.com/kb/changing-port-that-your-atlassian-application-listens-on-834000041.html
-
Ah, so it was the search, not the user. Thank you for the update!
-
Welcome to the community! What makes you think the count is wrong? I'll take one guess though - A Kanban board will show you *recently* done issues - older ones will quietly drop from view as they get old enough to be considered as not useful any more (2 weeks after they move to done and no-one touches them)
-
I think we'll need to see the configuration you've set up
-
The change of status must be done because you are removing the existing status from the workflow and hence the issues need to be changed to use the new workflow. It would make no sense to have issues in the status "closed" while their workflow is "open -> in progress -> done" - the closed status isn't in there. When you…
-
It's under General Configuration -> Advanced Settings
-
We don't know who your administrators are either - we're a community of people here to talk about Atlassian stuff. Some of your admins may be here, but the rest of us have less access to, or knowledge of, your system than you do! I'm afraid all we can do is suggest that you ask other users of the site, the rest of your…
-
You either need to give them accounts that can see the projects they need to see, or you could enable anonymous access to the projects, then visitors would not need to log in to see the issues (or search for them)
-
@Prince Nyeche - ELFAPP - I think a lot of us are trying to play this one a bit! For example, I said "a computer for non work stuff" - that could be anything from a small smartphone through to a serious gaming machine. I think you have another space, as "a phone" and "a laptop" are both "a computer for non-work stuff". Is…
-
Makes sense, there are a number of things that are global in Jira, rather than local to projects, and I think that's what you are asking about here. Jira tries to present a consistent UI or look-and-feel, and that flows over into the portals, they all end up looking very similar whatever you set up. There are some apps…
-
* A cat (assuming we can establish they're ok with the trip up and/or back, can adapt and they don't mind being called an "item") * A decent computer of some sort for non-work stuff, so one for a bit of gaming, tech tinkering, music, video, photos and so-on ( I'm assuming the ones on the space station should be restricted…
-
I am not sure of how Confluence actually handles the previews, but I do know it litters your installation with thumbnail previews, and I think (but I am not sure) that the thumbnails are done by page, not by file. So I suspect your page is creating a thumbnail, then when you change things, it's just falling back on the one…
-
We're mostly here to talk Atlassian, not Intellij, but in this case, some of us can give you a pointer IDEA needs an installation of a Java Development Kit on the machine you are going to run it on. You may have installed one, but whether you have or not, you have not told the operating system where it is for the current…
-
It could happen any time - it can take a while for Atlassian to go round every Cloud system and update each one, but they don't always tell us that very loudly. For a lot of the updates, it can be up to six weeks, but this one is apparently slated for a maximum of a week. Best case, it'll appear next time you log in, worst…
-
Your workflow is not clearing the resolution on the re-open transition (you shouldn't have a resolution of "to do" by the way, resolution being empty is what indicates that the issue needs something doiig)
-
It means that you can not set fields other than summary and description as mandatory (this is because the email reading process has no way to know what to set them to)
-
The WAR/EAR Atlassian releases of confluence are * Very very old * Out of support * Have known issues, including failing on some application servers, that were fixed in later versions (or stopped being a problem when Atlassian stopped providing WAR/EAR releases) What version of Confluence is this, and where did you get the…
-
Projects are mostly configured by schemes (and your service desks are project linked on a 1:1 basis - each service desk is a project). The schemes are globally available, with projects selecting them. What is almost certainly happening here is that your two service desk projects are using the same scheme for something. So…
-
So how else would you do this? Confluence's "this page has been moved to" is about the only "solution" you could usefully implement.
-
Project roles exist universally across every project, but then contain only project-local users and groups If you created a role of "Penguin wranglers" then you would see it in all your projects, but you could set up the projects like: * Project ABC - Penguin wranglers: Alice, Bob, Chuck and group zookeepers * Project DEF…
-
No, the issue key is the only unique identifier Jira knows of. It can't know that another field might be a unique identifier.
-
You'll need to talk to your administrators about this - they should be able to give you a valid url, or get the Jira that's supposed to be on that url back up and running again.
-
If you move a page, people landing on the old url for it will be given a "this page has moved to" message automatically. If you want to pro-actively redirect them, you'll need to create a new page with the old name and put a redirect chunk of code on it.
-
This error means that the Jira server cannot reach itself over your network. The two most common causes of this I see are * Poorly configured networks that don't allow the Jira server to resolve and connect to its own base url * Incorrect SSL settings - the Jira server can connect to itself, but has not been configured…
-
Fields hold data, they have no direct effect on what you can do with an issue, or how your workflow works, unless you choose to use the fields in workflow logic. Your boards give you a view of your issues based on where they are in your process - unlike Trello, Jira's boards are bound to your workflow, they show you issues…
-
A simple "get data from custom field" call will get a collection of users from a multi-user field, which you can then iterate over to get individual entries. However, that collection is not sorted, so there's not going to be a clear definition of "first". What is your definition of "first" here?