Peter Van de Voorde Community Champion

Monica, I don't think this is currently possible in Jira with the exisiting plugins. You could try to write your own plugin. Ormaybe you could try using Confluence for your todolists? You could just link your issue to the relevant confluence page and on that page you could use the task list macro to create your todo lists.…

Hi Monika, If I understand you question correctly you want the following: - In each workflowstatus sub tasks will be added to this issue as some kind of to-do list. - Once all subtasks have been checked off the issue can move to the next status. Is this correct? Best regards, Peter

Hi Tatiana, There is no out-of-the-box solution for this problem. You could create a mailinglist that contains all those email addresses and use the mailinglist address as the email address for the user in JIRA. But why do you need this? Best Regards, Peter

Hi Bih Luh, It's complicated because those applications are pretty complicated :) You could try to migrate your data using DB tools and then simply change the connection string but I would advise you to test this very thoroughly on a test system before doing this on a production instance. Best regards, Peter

Hi Bih Luh, Just follow the instructions in this KB article for JIRA: https://confluence.atlassian.com/display/JIRA/Switching+Databases#SwitchingDatabases-sametype For Bamboo simply follow the instructions in the link you already found. For Confluence read these instructions:…

Udo is correct in the fact that you can not use JQL for anything else than select queries. The following page explains how you can run your sql commands directly in the HSQL database: https://confluence.atlassian.com/display/JIRA/Running+SQL+commands+in+a+HSQL+database I hope this helps you out. Best Regards, Peter

Hey Christian, you can use this JQL to find the issues withing the Epic called test : "Epic Link" = test Cheers Peter

Here are the jira 6 release notes : https://confluence.atlassian.com/display/JIRA/JIRA+6.0+Release+Notes They should give you a nice overview.

What kind of comparision do you want? 6.0 is obviously better, nicer and faster.

Hi David You could try using an issue collector, there is no other way to limit access to certain issue types in a project. Some more information about issue collectors can be found here : https://confluence.atlassian.com/display/JIRA/Using+the+Issue+Collector Best regards, Peter

Hi Sirko You could add the jira dashboard gadgets to your confluence macro's as an external gadget provider as explained here : https://confluence.atlassian.com/display/DOC/Adding+JIRA+Gadgets+to+a+Confluence+Page That shoud give you a way to show filter results with 0 values. Best regards, Peter

Hi Martin, You can do this using macros like the Info, Note, Tip and Warning macro. Or with the Adaptavist Content formatting macro's : https://marketplace.atlassian.com/plugins/com.adaptavist.confluence.contentFormattingMacros Best regards, Peter

I can't really see anything wrong in your log file, could you take a look at the catalina.out in your confluence installation directory /logs ?

Is the Confluence you are importing to the exact same version as the one you are exporting from?

Hi Hendrik,Did you get any notifications in the atlassian-confluence.log file? This can be found in the home directory.Best regards,Peter

Hi Christian, I had the same question last year, I didn't find a solution then : https://answers.atlassian.com/questions/189619/making-sure-that-users-who-don-t-have-jira-permission-don-t-show-up-in-jira-when-using-crowd I don't think anything has changed since then. Best regards, Peter

Hi Mandy, Keep in mind that it's a very dangerous practice to start equalling story points to hours. People will start thinking in hours instead of story points and that will influence your scrum methodology. I do think the Cumulative Flow Diagram might indeed give you some of the insight you are looking for (as Justin…

Hi Karthik, this should be possible. you might want to take a look at the Jelly runner in Jira to do this quickly : https://confluence.atlassian.com/display/JIRA060/Jelly+Tags#JellyTags-jira:AddComponent You could generate a script and let it do the hard work for you. Best regards, Peter

Hi Karthika, As far as I know there is no way to do this. Why do you want to do this? Best regards, Peter

I didn't know about that one, thanks Jobin.

Hi Jeroen, I'm glad I could point you in the right direction. Could you please mark my answer as the correct one? That will mark the question as answered. Best regards, Peter

Hi Jeroen, Take a look at the Affinity plugin Clearvision is currently developing, it might be just what you need : http://www.clearvision-cm.com/affinity/#overview And they are currently looking for feedback, so they might be willing to listen and help you out. Best regards, Peter

Super :) Could you please accept my answer? This will signal that your question has been answered Best regards, Peter

Hi Kelsey, Simply click on the trashcan, this will remove the link between the Story and the Epic. Best regards, Peter

if it doesn't work, just send it to peter.vandevoorde at gmail dot com

Hi Kelsey, I got your screenshot. So your Stories are linked to your Epic through an issue link. Do you have any options if you hover over the Stories in the Epic issue? (does it show a cog icon on the left? ) Or even a trashcan icon? Best regards, Peter

Could you post a full screenshot of your Epic and all the stories that are linked to that Epic? And indicate which story you want to remove from the Epic? I don't want to give you wrong advice based on my own assumptions, a screenshot would probably clear certain things up. Best regards, Peter

Hi Kelsey, Are you currently using the Jira Agile or Greenhopper (old version) plugin? Or are your Epics defined any other way? How are you currently managing Stories and Epics? Best regards, Peter

Hi Kelsey, Simply edit the Epic Link field and set it to empty in your Story. That should do it. Best regards, Peter

You can do this easily in the planning view of your scrum board. Simply select the story in your backlog so you see the issue detail view on the right side of the page, go to the Epic Link field and click on the x next to the Epic name. Best regards, Peter