Comments
-
Try the issue.getParent call.
-
Crowd is a lightweight compared with Jira and Confluence, you'll probably struggle to buy a server that can't handle it nowadays. I know of one running on a raspberry pi with 1 Gb Ram, for a small site with only 20 users. It seems fine to us, although the pi is running only a cut-down OS, Crowd, some basic monitoring and a…
-
Remember that the permission scheme may be different - it might not say "edit: role (developer)".
-
Have you tried a new download?
-
The doc works for one of our clients who wants to reduce their security this one, so the question is what you are doing differently to the doc? And yes, I did say "reduce security". Disabling autocomplete is a bad security pattern. It encourages people to write down and reuse passwords and to use the most simple one they…
-
Ok, it's moved again - look on the left in the blue bar for "turn off for now"
-
Yes, all the zip files are complete backups, so you only need one. My paranoid mistrust of computers doing a perfect backup every time makes me instinctively keep the last 3 or 5 so I've got something just in case there is a glitch with the export, but yes, you should be absolutely fine with just the one.
-
Permissions are done at a page level in Confluence. If you can edit a page, you can edit all of it. Also, Confluence doesn't have the concept of roles like "owner", permissions are by group or individual.
-
GO into your profile and look for the "use old layout" option, that will take you back to the previous version of the UI. However, this will not be permanent, Atlassian are going to remove the old UI at some point, and you will be stuck with the new one. I don't know when this will happen.
-
Start at https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-reports-732528965.html
-
Have a read through of https://confluence.atlassian.com/doc/configuring-backups-138348.html
-
A lot of the answers you've found apply to current versions of Confluence, not just "previous". Cloud Confluence does have versions, but they're mostly irrelevant to you because Cloud is upgraded automatically and you can always assume it is latest or only one release behind. But the answers don't apply to Cloud because…
-
It looks like you have not included the existing issue key to tell the import it needs to be an update. With no existing key, it is looking to create new issues, and then spotting that you already have issues that have the same summary, so it's not creating duplicates. For updates to existing issues, you need to give it…
-
As an admin, go to the project configuration (Admin cog -> Projects -> your project.) Find the "permission scheme" it has been given and go into that. You will find it has a rule for "browse project" that your account does not match. It will be something like "Role: users and project lead". That should tell you what role…
-
Search and the project listings are the only places Jira uses the category. So it should be just your filters you need to update.
-
You need to remove the "everyone can see everything" rule from your permission schemes, and then you can add your single user back in.
-
Stock answer: Do not think about it. Atlassian use databases as data stores, not real databases, and using SQL is for complicated bug fixes, and a handful of queries where the UI is weak. Most of the time, using SQL is, quite simply, wrong. Whatever you think you need to do here, doing it with the database is almost…
-
Start by deciding where you want to code. Confluence can reach into Jira and fetch simple data, so if you code in Jira, you can provide that. But the fetch is going to be simple and just get simple strings, numbers, dates or users. But if you code in Confluence, you can ask Jira for simple data and then (re)format it for…
-
Miss what?
-
I have to agree. Synchronisation was a route worth exploring, but you still have to open up a route for it (unless there's one like "email" already there), and you'll be doing that with VPN anyway. Technically, VPN is the best answer, as there's no duplication or working in separate places and gives you full access with…
-
The greenhopper stuff is really very old, and you should be importing Jira Software stuff really (Although it's not been refactored in full, so there are references to GH and Agile in it still)
-
Might want to attach a screenshot?
-
Could you tell us more about "unable to add"? Are you able to get to the quick filter list at all? Add text? etc?
-
Yes, the "please select" option came in a while ago.
-
It's a bug in the workflow editor, it won't let you add transitions to status that don't have ones when you're in draft mode. You'll need to cancel your edits, copy the workflow to a new version, then edit that. Then go into the workflow scheme and swap the old one for the new one.
-
Comala is not an add-on for Jira. Are you talking about Jira or Confluence with Comala workflows in it?
-
Ok, they must have been coming from other add-ons then. I thought those are the only three immediately available in Cloud However, adding them to server should have added to the list of validators - are they showing as installed and active in the "manage add-ons" section?
-
Thanks! This tells me that there's something structurally wrong with your system. Can you get to the "system information" page in the admin section and check for "modified files" and give us the versions of Jira and Java in use?
-
Most custom fields need objects that represent their content. For numbers, that's easy - int, long and doubles can all go in. Text fields expect strings, dates expect Timestamps, and so-on. The Jira specific types are ones like users and "options" (for most fields that are selects or radio or checkmarks). Field with…
-
No, I mean that sub-tasks do not have security levels. Even if you manage to get the field on them, and put a level in (which is where I'm confused about how you think you've done it, because the UI won't generally do it) it is completed ignored