Comments
-
If there is no update option, you're on the latest version valid for your system. There is no downgrade option here.
-
Book time for a full re-index (not the background one). I suspect you'll struggle to find an error in a filter caused by this discrepancy. Why are your users looking at the index anyway? The way it works in the background is not relevant to them, and the discrepancy you're reporting is unlikely to actually be a problem.
-
Then there's no name to be changed. My guess is that you do not mean the standard JIRA "components" field, and you've got a custom field with that name. Only JIRA or system administrators can rename the options in custom fields Or you might be using the word "components" to describe something else. If it's not components…
-
This is probably the default permissions. Your users will have been added to a group that says "can log in". This group is probably also being used to provide "browse project" in the permissions. You'll need to unpick that if you want to restrict them - create a new group or groups separate from "can log in", put the right…
-
You should use the "manage applications" function to do the upgrade of Service Desk. It makes sure you use the latest valid version of the application.
-
You can, but you won't like it. Retrieving the data on-screen for a single issue can be 30-40 "joins" in SQL. It would be far better and easier to find (or even write) an addon that can do the reporting you need.
-
I assumed you'd coded to bypass the permission, which would be a lot better than hacking the core code.
-
Yes, that's right.
-
The reasons are varied, could be a server crash, a dodgy plugin, a bug, or even just an unforseen clash with a disk write action. The solution is a simple one -reindex the whole lot. Minimising this discrepancy is almost certainly not worth the effort. If it was a huge one, that built up rapdily, I'd be looking at why it…
-
That's a good aim, you want to keep it clear and simple, and "if it is done, it is not backlog" is exactly right. There's three things to look at here to begin with. 1. Check your board's column configuration. The important thing here is that the last column on the far right hand side of the board contains the status…
-
There are several possible variations on an answer to this question, but we need to know what type of board/backlog you are looking at to cover the finer points. There is a short answer to cover most cases though. Check that your issues have a resolution, and that when your board selects them, the filter and column config…
-
Yes, you enable "anonymous access" And note that it doesn't have to be global - a lot of places have a Confluence with a batch of public spaces and then a whole load more that you have to log in to get to. Have a look at https://confluence.atlassian.com/doc/setting-up-public-access-156.html
-
Start with issue linking, they're directional (e.g. X blocks Y, Y is blocked by X), you can define your own link types, and there's some reporting that can help you with them too
-
If you're on an older version of JIRA Software, you may not have that permission, it's a relatively recent addition.
-
Yes, sorry, I was assuming "page exports" were being done with mass space exports. I should have stated that properly!
-
I assume you mean JIRA? It's not clear if you are talking about emails arriving and creating issues, or the outgoing emails from JIRA?
-
There's the full xml backup which will contain everything and can be used to import into another Confluence if you want to go that way, but otherwise, the page exports are the only other option.
-
If a screen is set on a transition, it will appear for all users using that transition. Are you sure they are all using the same transition?
-
Ah, you meant the "status category" for to-do, in-progress, done. But they don't have any effect on the workflow, they're just for grouping and displaying status. There's also project categories.
-
It's not unreasonable, but from the code I've been wandering through, it's not easy. Especially as just accepting external directories doing it already clobbers performance.
-
A 403 error means "the server has refused to give this page to you because the security is configured not to let you see it". JIRA does not have any functionality that does that. A user who can't see something gets a JIRA page with a message telling them that JIRA is not letting them get to it. A 403 is "you can't see any…
-
Remove the permission for a user to log work.
-
You don't. Confluence doesn't have nested groups. It can understand the nested groups provided by some directories, but it flattens them out.
-
You need the *home* directory for the server - I can't tell you what that is, but the system information page will. You don't need to copy the *installation* directory, you should stick with what you've installed on the test server. Once you've copied the home directory, you should edit the file in the root of the home…
-
Most likely problem is that you have not shared the filters that the dashboard relies on.
-
That suggests that you've put some form of filtering in front of it to prevent people getting files of certain types.
-
Your query says "created before 2017-04-04", not "created on or before 2017-04-04" Try changing the < to <=, or use 2017-04-05
-
I'm not aware of any specifically open-source ones. I look at the features my clients need and then cost. If cost is the primary thing you need to worry about, then that's fine, but I'm afraid I can't really suggest or recommend any product. You need to decide on what you're looking for and then have a look through…
-
Sorry, the coffee is weak today. I forgot. Annoyingly, project management type projects do not get the release reports and options that Software projects get. Try changing the project type.
-
You don't, they're already enabled. (Assuming you're not on an older version)