Peter Van de Voorde Community Champion

Hi Ashley, Yes the user will have to login twice, both times with the same credentials, If you don't want this you should take a look at implementing Single Sign On with Crowd. I do think Confluence caches the user information in the database after their first successfull login, but it will always go back to JIRA for…

Hi Ashley, JIRA and Confluence will still be separate applications, so your user will need to login to both JIRA and Confluence separatly. What will happen is the following: When a user wants to log in to Confluence Confluence will ask JIRA the following: * Do you know this user? * Is the password correct? * Can you please…

Hi Ashley, When using JIRA for user and group management the biggest advantage is having one central location for all your user management needs. But if you already have an LDAP in which you can manage the users and groups this advantage doesn't really count anymore. When I have the combination of JIRA, Confluence and LDAP…

There seem to be some wierd characters in your email signature. You could simply try to find out which is the exact offending character and remove that from the email signature. Best regards, Peter

Hi Rahul, First off : you always work on a draft of an active workflow, and only when you push the publish this draft button the changes will actually be executed in the active workflow. So if you simply do all of your changes in the draft of your workflow and then publish the draft it shouldn't give you any problems. To…

Hi Mark, Why don't you make the field required on the Open -> In Progress transition? They will still be able to add the stories to a sprint but they will not be able to start them untill a value is filled in for the Story Points? But as Kim says : it's really a team issue. Ask them why they aren't doing it? Don't they see…

Hi Tiago, This is not possible in Jira Agile. As a scrum master I would solve this by notifying the team during the daily standup and help them prepare for the next sprint. I don't think this is an issue you should solve using tools, solve it using your team. Best regards, Peter

Hi Robert, It is possible to link OnDemand and hosted applications. Do keep in mind that user management and stuff can be a bit bothersome because of the fact that OnDemand has it own user management. Why are you considering doing some on OnDemand and some on Hosted? Won't it be easier to simply do all on OnDemand or all…

Hi Mark, You can log a new feature request here : http://jira.atlassian.com good luck! Best regards, Peter

Hi Deepak, Why are you posing the same question over and over again? Please respond to previous answers and comments. Best regards, Peter

Satyakam, Then I wish you good luck on your endeavour. Maybe this documentation might help you too : https://developer.atlassian.com/display/JIRADEV/Database+Schema Best regards, Peter

Satyakam, Why do you keep on pushing this ETL solution when 3 people already explained you in detail that this is not the way to go? Both Nic and Udo know what they are talking about, when they suggest not to do it with an ETL I would listen. Best regards, Peter

You cannot, as Udo points out it's not nullable, so you can't ignore it.

Hi Satyakam, To give you a simple answer to your question : Using ETL does only have disadvantages compared to using the build in JIRA import utility. So don't do it. Udo clearly explained why. Best regards, Peter

You could work with linked issues, but it's currently not possible to put sub-tasks in sub-tasks. I don't know if this is in the development pipeline.

Yes that seems to be the case. But only for the pop-up Create Issue Screen. If you have the full screen wizard it will simply show all fields. Best regards, Peter

Hi Christopher, This is caused by the fact that you selected the custom option in the Configure Fields option when creating an issue. As explained here : https://confluence.atlassian.com/display/JIRA/Creating+an+Issue JIRA will remember the last way you viewed the create issue screen. So if you change it to All it should…

Hi Christopher, You'll need to check which screen is being used for the Create Issue action in your Screen Scheme. You just need to add the fields to that screen using the Screen Administration Page of JIRA. More information about Screen Schemes can be found here :…

Hi Reiko, I would contact https://support.atlassian.com and ask them to help you out. As this is a problem in On Demand, they are the only ones who can go and take a look in the log files for you instance and fix it for you. Best regards, Peter

Hi Stefan, I'm sorry but there is no bulk configuration option for field configurations. Best regards, Peter

I hope it worked :) don't forget to mark your question as answered by accepting my answer :)

Hi Rahul, Go to your Global permissions menu in the JIRA administration. Give the group Global Jira Administration rights. Then you're done :) Best regards, Peter

Hi Maitreya, You'll need an account with admin rights so you can check the project permissions. You'll probably need to change the permission scheme or add yourself to the correct project role to get Project admin rights. More information about permissions can be found here :…

Hi Rog, I can see how that might indeed cause problems if you want users to be able to do all of this and if you have so many different labels. You could always create a feature request (Story) here : https://jira.atlassian.com/browse/GHS You can always work with two screens and on screen have the backlog and on the other…

Hi Rog, You could try and use quick filters based on your labels. You can configure them using JQL in the config section of your Board. Just create some quickfilters like this : labels = "My-favourite-Label" and save them. Then if you click on the quick filter on the plan backlog screen it will only show those issues that…

Hi Nuno, That's not possible with you version. You could upgrade and take a look at enabling auditing : https://confluence.atlassian.com/display/JIRA/Auditing+in+JIRA Best regards, Peter

Hi Nikita, I don't think this is possible, you could exclude the issues in the status done from your greenhopper board completely by excluding them from the filter that's behind the board (this can be configured in the configuration screen of your greenhopper board) and then they aren't shown in the issue count per…

Hi Alain, Do you get any error in in your confluence log files? Best regards, Peter

Hi Paul, Are you using Jira Ondemand? Or a hosted solution provided by another party? Best regards, Peter

Hi Drazen, Could you upgrade your Jira to the latest version (6.1.2), I hope that should solve it. Best regards, Peter