Comments
-
Did you also delete the broken resolution?
-
Ah, I completely forgot - security does not apply in the new issue view, nothing has been implemented for it. The level should not even appear when creating an issue.
-
Confluence does not do this, it is collaboration and co-working software, not software for reducing sharing by creating network blocks. To restrict IP access, talk to your network administrators.
-
A "stand up" meeting is a meeting intended to be short (and one good trick for persuading your humans to keep it short is to have no seating). In "Agile", the idea of a stand up emphasises the short - each person speaks, uninterrupted, about what they achieved since the last one, what they're doing now/next and if they…
-
It's simply picking the first status it finds. You can't change it directly, from memory, it's based on the id of the status - first one it finds in the workflow gets used.
-
The software I've mentioned is there to synchronise between instances of Jira Core, more than JSD and Software. But, JSD and Software are layers of functions that sit on the top of Jira Core issues and projects, so even if those two completely ignored JSD and Software (they don't), they would still be synchronising 95% of…
-
Are you running the installer as "confluence"?
-
There's not a lot we can help you with here. You need to look at the operating system to see why it cannot save the file to the disk. Try logging in as the user that is set up to run Confluence, then * cd /var/atlassian/application-data/confluence * cat confluence.cfg.xml * touch confluence.cfg.xml You will get an error…
-
You will need to install it on a server, make sure that server has a static (or always resolvable address) on your network, and give your users the url to reach it.
-
What are the status and resolution of the Epic? (Resolution may be blank/unresolved, - it might not have one of those)
-
Are there any sub-tasks on this issue? If there are, what status are they in?
-
Percentage of what? What units are you using to define "complete"?
-
What does "where's my field" tell you about the "level" field?
-
Yes, that will cause you problems. You have a corrupted database now. I would try restarting Jira and running the integrity check. That may be able to repair the tables, but if not, then I suspect all you can do is export the issues and import them into a working Jira.
-
Yes, that looks like you've not quite got the database settings right, although good enough to get in, to find there's no valid data there. Could you set up a new, empty Jira with a different database next, same version as you had before. Prove it works by going through setup and config, logging into it and checking you…
-
So those errors could be leading to the deadlock, not the other way around. You should examine them to see where they are coming from.
-
No, an application link does not allow you to throw issues from one system to another. You have totally separate systems here, and "convert" is only possible within the same system. Linking is all you can do (without code/apps) If you're interested in synchronising these systems though, have a look at Backbone and Exalate.
-
Could you create a test issue, selecting a security level for it. Go do something else (there's a minor bug I've seen where a field disappears if you go straight into the issue view) then go back to the plain issue view, ideally using the url direct (https://yourjira/browse/ABC-123) Click "edit" to get into the edit screen…
-
Connect - yes, set up application links for them. You'll then need to explain what you want to use these connections to do?
-
I've seen it used for HR, Legal systems, logistical track and trace, sales, organising events and trips, and heck, even house moves and weddings!
-
Which vulnerability? All we've got there is 7.12.1 which has a number, mostly fixed by "upgrade" as recommended by Atlassian.
-
The place to get apps is https://marketplace.atlassian.com/ (also accessible from within the applications!) There are a load of reporting apps in there, several of which would be able to do this (and a lot more). I'm not sure I've seen a lightweight one which would just answer that one question you have and do little else…
-
What do you mean by "root workspace"? The domain you are on? Or the name of a page at the top of your "workspace"?
-
That suggests you either do not have permission to see it, or the scrum board's filter excludes it, or the issue is considered "done".
-
That does make sense - when you put value X on a field, you expect it to stay there until someone changes it, or the value for X has changed. You've not really said to do either of those with the context change, you've changed the list it draws values from. So the issue will retain X until changed.
-
Yes, but it is a separate and very different licence. For Jira, you licence Jira users, they get project access, and can then work with issues. For Jira Service Desk, you licence Agents, and they get project access, can work with issues, but can also set up and deal with requests from "customers" in the projects behind the…
-
What is the base url for your Jira SD installation?
-
Ok, well, that's a fully supported version of Jira + Database + driver + connection string. I think the next step is to find that error in the main log file and look at the errors that are occurring immediately before and after it.
-
Yes, all issues in a project are affected when you re-configure a project.
-
Yes, especially if you use the "Jira Service Desk" application.