Peter Van de Voorde Community Champion

Hi Andrew, Only people with Super user rights can do this, so for OnDemand that means Atlassian Support. Just send them a request to remove the space or to grant you access and rights to this space so you can remove it yourself. Best regards, Peter

Like Nic says : could you please provide the full query?

Which error do you encounter?

Hi Krystian, You should check your log to see if there is some information that can help you. If not, please contact Atlassian support here : https://jira.atlassian.com/browse/JRA Best regards, Peter

Hi Kriss, I've just tested this on our Confluence 5.1.3 instance and I didn't get any errors. You could try to access the page using the pageid using this type of url : http://<your-confluence>/pages/viewpage.action?pageId=6062574 Best regards, Peter

Hi Neil, If you make seperate user groups for all your projects and use these groups in the project permissions that should certainly be possible. For example a user in group A will only have access (and view) project A, while a user in group B will only have access (and view) project B. A user in both groups will view…

Neeta, I just reread everything you've said so far. I think you just need to remove the email adres from the Forward Email field in your Email handler. Don't check the create users box and don't fill in the default reporter. I hope that will help solve the problem. If you do fill in a default reporter a ticket will be made…

Hi Neeta, If you do not check the create users box you'll need to fill in a default reporter (as reporter is a required field in Jira). This can be a user you've created especially for this purpose (for example : Mail-user) If people who do already have an account in Jira will send an email this default reporter will be…

Neeta, You'll need to fill in the following field : Best regards, Peter

Hi Neeta, Did you fill in a default reporter in your mail handler? And has this default reporter perhaps the same email address than your jira? Best regards, Peter

Hi Neeta, This is probably caused by the fact that you disabled create new user check. If you disable this then somebody who isn't a jira user can't create a ticket unless you have filled in the Default reporter field. What is the error message you are getting? Best regards, Peter

They can also just click the assign to me link underneath the Assignee dropdown box. Then both your workflows are possible.

Hi Neal, You could vote for this issue : https://jira.atlassian.com/browse/JRA-33862?jql=text%20~%20%22component%20full%20list%22 Or create your own feature request in the Atlassian JIRA. Best regards, Peter

Hi Milan, I would follow the resolution before executing the upgrade. Best regards, Peter

Hi Kathy, This is because you can only select fields that have finite values for a pie chart. The Original Estimate field can have an infinite number of values. Best regards Peter

Hi Sai, Next to being an Atlassian Expert for my company I'm also an ALM (Application lifecycle Management) consultant. I focus on improving 3 pillars that support the full ALM proces: People, processes and tools. It's clear for me that the problem your client has will not be solved by the tools. He should find out why his…

Hi Sai, Just wondering: why exactly does your client want this so badly that you will need to start developing a plugin? Isn't it cheaper for them to use the workaround I provided? Best regards Peter

Hi Sai, You could ofcourse also do something else : * create a new version with the new name * do a bulk change on all issue currently part of the old version and change the version to the newly created version * delete the old wrongly named version That should do the trick. Best regards, Peter

Hi Arpit, Go back to your original Confluence (before the export) and take a look at the usernames that were mentioned there. Do they exist in your CROWD directory? Are they written exactly the same? (Uppercase, Lowercase...) Do they have the same permissions? It might be one of those things that's causing the problem.…

Hi Marcin, You could simply make the post build task a final task in you Bamboo job. Take a look here for more information : https://confluence.atlassian.com/display/BAMBOO/Configuring+tasks Best regards, Peter

Could it be that your confluence and jira instance both use a different jre? And that you have to import your server certificates in both keystores?

Why do you want to hide this button?

Hi Zubo, JIRA Agile considers sub-tasks to be a integral part of a Story, so it wouldn't make sense to schedule some sub-tasks of a story behind sub-tasks of other stories. If you did it like that your stories wouldn't be finished. If you use sub tasks in Stories you'll still get the nice Time Tracking (including sub…

Hi Zubo, I'm confused about what you are saying, in JIRA Agile you can still use Tasks and sub-tasks just like in JIRA. An Epic is a collection of Tasks (or Stories) which is at a higher level. You could take a look at the Epic reports underneath the report mode of JIRA Agile to see if that report gives you the information…

Hi, You can find more information about Bamboo and Elastic here : https://confluence.atlassian.com/display/BAMBOO/About+Elastic+Bamboo https://confluence.atlassian.com/display/BAMBOO/Working+with+Elastic+Bamboo https://confluence.atlassian.com/display/BAMBOO/Configuring+Elastic+Bamboo…

Hi Nancy, You could try the following: * add the not existing status to the Epic workflow. * move the faulty Epic back to Defect * remove the status from the Epic workflow. Best regards, Peter

Hi Rinku, I just wanted to make sure that we are talking about the rigth edition :) To see the order of the user directories you should go to your Confluence Administration page and search for the User Directories menu. This should contain both your internal Confluence Directory and your LDAP directory. Here you can see…

Hi Rinku, I just noticed that you are using conflluence on demand. That isn't even able to connect to an ldap, so are you sure about the information in your question? Best regards, Peter

Hi Rinku, How are you creating the users? (Through Confluence or Through LDAP) Is your LDAP read-only or read-write for Confluence? In which order are you directories in the user directories administration screen? Best regards, Peter

Hi Ulf, I don't think we can help you, you should raise a support ticket with the Atlassian support. You can do this here : https//support.atlassian.com Good luck on fixing this. Best regards, Peter