Comments
-
Ok, then you'll want to raise this with https://support.atlassian.com - tell them the date/time of the last time you got the error message and ask them to tell you what the logs say - that will probably explain it.
-
Hmm. Do the logs just stop dead then? You have normal lines in them and then they just end? What are the last 10 lines in atlassian-jira.log and catalina.out ?
-
What do the logs say the error is when it crashes?
-
Depends on your permission setup. A standard / recommended setup will be using roles to allow people into projects, and project admins can maintain who is in what role in their projects. If it's not set up with roles, then your JIRA or System admins will need to alter people's groups or update permissions.
-
An "import failed" will write to the application logs. You need to get those and read them to see what the error is.
-
And the logs?
-
That one is mildly annoying. Atlassian look like they're not going to do anything about it, but have a look at the bug report for something very similar. https://jira.atlassian.com/browse/JRASERVER-61781 has a simple "put file on server and restart" workaround to get it to shut up and stop bothering your users.
-
Is it the same error? What do the logs say?
-
I'm afraid "customers" only get portal access. That's the interface for them to raise and track their requests. There's no dashboarding or reporting in that - it's built to be a help-desk type interface. If you want them to use dashboards, then you will need to allow them into JIRA as standard JIRA core users. That does…
-
Have you added the field? The add-on just creates a field type, not a field. After creating the field, you also need to re-index before it will become useful.
-
Cloud has been around for many years, so I don't think you mean that. I suspect you mean that Atlassian accounts have been more tightly integrated into Cloud systems, and people moved from local accounts to Atlassian accounts. I'm guessing your authentication code used to try to authenticate people by trying to log them…
-
The only safe and quick way to do a "downgrade" is to restore the backup you took before the upgrade.
-
Edit the workflow and place the "do not edit" workflow property (jira.issue.editable = false) on the "closed" status. You can see an example of it if you look at the default JIRA workflow, and see https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html
-
Natively, you can't do it. You need add-ons that can provide "field level security" or fields that are aware of their context. At the risk of advertising, the only one I know that does "field level security" for a wide range of fields is the Quisapps one. There could be others in the marketplace, but I've not looked.
-
Are you spellling the property correctly? That's the mistake I usually make.
-
You'll need to read the logs to see what is going wrong. When it starts up, I'd expect some form of "can't communicate with database" error, with some reason it can't log into it.
-
Assuming you mean JIRA, then yes. Have a look at the "workflow scheme" for the project, which will tell you what workflows are in use. Find the one for "task" and make a copy of it in the admin screens. Add the new ice-box status to it and change the "create" transition so it lands there instead of to-do Go back to the…
-
Have you got the next sprint ready to go (but not started)?
-
We are end-users, like yourself, and don't have any access to your systems. You'll need to talk to your administrators - get them to check the permision schemes on those project and work out why you can't see them.
-
You'll need to find or write a "listener" that can pick up any event where the field might be updated, and issue a workflow change based on it. Have a look in the marketplace, you might find it easier to work with an Automation or Scripting add-on than start from scratch on your own.
-
>1 at "fixed" status but not installed yet (so with no fix version) Ok, that's where the "one unscheduled" is coming from - the no fix version is pulling it up. What I think is broken now is the "is empty" should find that too. I'd still try a project re-index. Admins should be able to do that from the admin options on the…
-
There's not a lot we can tell you here other than "plan". There are two layers to look at: First - the users and groups. There's no information in your question about what you have providing your user lists or what you want to end up with. So we can't tell you anything. Most directory systems will have at least the…
-
You'll want one that understands the JIRA database properly. There's quite a few around, but I'd lean towards EazyBI and Arsenale's Dataplane. They're very different beasts, so it's worth a look at both to compare them for your needs, and any others you find in the marketplace.
-
Ok, great. Two more tests What does "project = xxx AND status = Done AND component = Comp1 AND fixVersion = Unscheduled" give you? One issue or none? (Or many? Which I don't expect, but could happen) Can you reindex project xxx and see if that helps?
-
If you've imported the data from a production system (which is usually a very good way to make a test system!), then I would say your system has inherited the user directory setup from there. And that user-directory system is either read-only or not available to your development system. Go to Admin -> User directories and…
-
Yes, there's a lot of changes. But if your sidebar is broken, it's not Confluence itself doing it, it's something you have configured - either an add-on or a css/html customisation in your system. Check for those and (temporarily) remove them to see what might be breaking it.
-
Could you try running a filter for "project = xxx AND status = Done AND fixVersion in (dev, prod) AND component = Comp1", save it, and put it into a "filter statistics" gadget, with "fix version" selected as the statistic? What numbers does that give you?
-
Assuming you mean JIRA, the easiest optionis probably to use "message fields" from the "jira toolkit" add-on to create some form of separator field in the displays.
-
The index files are damaged in a way that makes them unreadable. You'll need to clear them out and start again. * Stop JIRA * make a backup copy of everything under $JIRA_HOME/caches/indexes * delete everything in $JIRA_HOME/caches/indexes, all files and subdirectories * Restart JIRA - it won't work properly on the…
-
You can change the url, but it's not a real "change", it's a "copy and delete". See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html