Peter Van de Voorde Community Champion

Ian, Did you change the server.xml file? Maybe you did something wrong there. Also did you maybe do something in the hosts file? Best regards, Peter

Hi Dario, You can import a project from the complete backup file of a JIRA instance (using the project importer tool in the administration pages). But this will replace your existing project and data with the new one (which not what you want is seems). Using the project configurator provides you with an easy to read xml…

Hi Dario, If you need to be able to recreate all schemes and custom fields you should take a look at the project configurator plugin: https://marketplace.atlassian.com/plugins/com.awnaba.projectconfigurator.projectconfigurator Best regards, Peter

Hi Patrick, I deleted my old answer, it wasn't relevant to your problem. Can't you work with rules on your inbox to triage the emails based on text in the subject? Move the issues to different folders and let seperate email handlers read those folders. Or you could create something like a global support project which will…

Sorry, I hadn't seen you were using OnDemand, my mistake

Hi Patrick, I would advise you to take a look at the JEMH plugin for JIRA. This already provides a wealth of possibilities using email and JIRA and is super well supported by it's developer Andy Brooks (who's a very active member of this community). https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui Best…

Hi Julien,I just found it and tried it on the latest spammer, but even after confirming to ban this user in the pop-up it doesn't do anything. Best regards,Peter

It seems we can no longer instaban spammers, which was a feature available once you had enough karma points. Will this be coming back?

Hi Rong, Couldn't you simply change the permission scheme of your project so only admins can delete issues? Best regards, Peter

Hi Marwa, what do you mean with sso feature? If you only have JIRA your users should only log in once. If you have multiple atlassian applications you should take a look at Crowd for an SSO implementation. Best regards, Peter

Hi Hüseyin, You can follow the instructions in this manual to add all the gadgets that you have in Jira to your Confluence pages. https://confluence.atlassian.com/display/DOC/Registering+External+Gadgets Best regards, Peter

Just wondering, as an issue can be part of several versions (both fix and affects) how will you choose which release date to show? Couldn't you just better set a due date for the issue? Best regards, Peter

You might find some help in the following locations: https://answers.atlassian.com/questions/71257/how-to-migrate-jira-accounts-from-local-to-ldap https://answers.atlassian.com/questions/102983/migrating-to-ldap-for-jira-and-confluence…

Hi Jamie, As you are on an On Demand instance you might want to send a question directly to Atlassian Support too, they might find something in the log files of your instance. Best regards, Peter

Andy, Can you ping your server? Is it reacheable inside your corporate network? Best Regards, Peter

Just wondering, might it be that you closed the Command Line window in which the confluence tomcat was running? If that's the case then your instance is currently offline. If that's not the case or if you are running confluence as a service (and it's currently started) you should indeed check the logs like Nic suggested.…

If you buy the greenhopper plugin, it has build in epic functionality. You could also use components as epics, or even labels.

Hi Hubert, This is not possible, an issue will be shown in the first swimlane it can be part off. Best regards, Peter

Hi Rahul, Again at the moment this is not possible. You would need to give your users access to JIRA and help them create a dashboard there. Best regards, Peter

Hi Rahul, This is currently not possible using the JIRA Service Desk Customer Portal. This is possible using JIRA dashboards. Best regards, Peter

Hi Stéphane, I took a look a the same kind of solution but didn't trust it enough. Especially Foreign keys and ids generated by the database would make it extremly tricky. You could always keep a read only copy of your old jira instance for historical reference. Best regards, Peter

Hi Stéphane, I've had the same problem a couple of months ago and couldn't find a solution. In the end we decided that we didn't need the agile history as much as we just needed the issue history (all important information is in the issues not the sprints). Best regards, Peter

Paul, You can edit the filter behind your board (through the board configuration screen). Simply remove all issues with the status closed from this filter, then add the status closed to your Closed Column. You'll be able to move issues to this column but they will not polute your board. Best regards, Peter

Hi Rita, Do you Bamboo and JIRA have the same user base? Does the user Atlassian Bamboo exists in your JIRA instance? Does it exists in your Bamboo instance? Is this user part of the correct user groups (Bamboo-user and JIRA-user)? It seems that the user you are using to connect from JIRA to Bamboo doesn't have rights in…

Hi Calogero Simply go to you confluence installation directory, find the bin directory and there you'll find several .sh scripts. Simply execute ./stop-confluence.sh or ./shutdown.sh you can use ps -af | grep confluence to see if the process has actually been gracefully shut down. If this didn't happen after a few minutes…

yes it will. good luck :)

jira-users jira-developers jira-administrators those are the 3 basic groups. good luck Peter

Brian, Yes you'll need to create those groups in the AD too. Now JIRA will look you up in the first user directory it encounters (AD) and will try to get your groups from that directory. If you don't have any groups : bad luck... Best regards, Peter

Brian, Did you add you LDAP account to a jira-administrator group in LDAP? If not then it doesn't recognize you as a jira-administrator. Best regards, Peter

Hi Jozef, JIRA-USERS might be seen as a different group then jira-users (even if the search user in group functionality works). Could you please try to rename your AD group to lower case jira-users and try again? Best regards, Peter