Peter Van de Voorde Community Champion

You could use your t-shirt sizes as a first estimate for the complexity/size of your issues. But Greenhopper needs numbers (hours/story points/...) to calculate things. I would recommond you to use T-shirt sizes (in a custom field) to quickly triage your issues and then do a poker planning estimation by story points for…

Hi Chris, As you already pointed out: there is no true difference between a Story, a Feature or a Task in JIRA Agile, only what you and your team make of it. If you need to break certain Stories up into items that have to be assigned to different teams I would advise you to convert this Story into an Epic and make new…

You could put back a copy of the repo on the old host. Startup Bamboo, change the repo and remove the copy on the old host. Just an idea. Best regards, Peter

Hi Sergio, This is all saved in the database and it's a really bad idea to start playing around there. the easiest way is to simply use the UI to change the repository. You can also take a look at the Bamboo CLI : https://bobswift.atlassian.net/wiki/display/BCLI/Examples It does have an updateRepository action. Best…

Hi, Epic is not a standard issue type in a vanilla Jira installation, so it might be that you do have the Greenhopper plugin (you can check this easily : if you have an Agile menu next to your Issues menu in the top menu bar of your Jira Instance then you have Greenhopper installed). If this isn't the case then you can…

This is pretty complex, and what are you going to do when 2 of your people had the same issue assigned to them?

Hi Manu, First off : why do you needs such big attachements? Isn't it better to set up a dropbox/google drive/ftp server type of system to which you can just redirect people using a link in jira? As Tanner said : you can easily raise the attachement size limit in the admin module. This will mean that your virtual machine…

Hi Wilhelm, You could use Jelly to create script that automatically creates a project. More information can be found here : https://confluence.atlassian.com/display/JIRA/Jelly+Tags#JellyTags-jira:CreateProject Best regards, Peter

Hi Christophe, You could put the role specific fields on screens that are only used when transitioning from on status to another. If you do this and don't put the fields on the edit screen you can then use the transition validators to indicate which role can execute this transistion and consequently edit those role…

Hi Johannes, Could you please accept my answer? This will mark your question as answered. Best regards, Peter

Hi Johannes, I would simply create a project per Bakery (so one for Alice's Bakery, one for Tom's Bakery) and use these projects to contain all stories that are custom for this customer (design,...). I would then create a global project which contains all you common stories (the core functionality). You now have a clear…

Hi Mike, And what about the second suggestion I make? Then you'll have only one email address. You could also create a global support project and let somebody dispatch (move) all the issues to the correct projects. Best regards, Peter

Hi Mike, Couldn't you simply create several email address and mail handlers, one per project? And just let your people send emails to that address. If they don't have create rights in the other projects they will not even be able to use those other email addresses. And from your explanation i conclude that most of your…

You could try something like that if you don't have SSO configured through CROWD but it might be a security hole. Why don't you give those customers JIRA access too?

Hi Susanne, This will only work if you make the JIRA Project browseable for anyone (so for anonymous users). Best regards, Peter

You should use your variables in the query string, like this : String query = "insert into jiradb.dbo.testworklog values("+namevalue+","+desvalue+","+rolevalue+")"; Best regards Peter

Hi Liesa, Do you get any more information about the problem in the atlassian-jira.log file in the <jira-home-dir>/log directory? Or in the catalina.out log file in the <jira-install-dir>/log directory? Best regards, Peter

Hi Mehran, Maybe you could just try it out in a Demo project you create on your machine? I would think that it's simply in the order that they are created. I can't check it on any of my jira instances because they are at least version 5.x Best regards, Peter

Hi David, Jira normally runs on port 8080 and Confluence on port 8090. Maybe that's your problem? Best regards, Peter

Hi Scott, Even when your Confluence space is visible anonymously the JIRA issues will only be shown if they are also visible anonymously. To do this you'll need to make your project(s) and the issues within them visible to anyone in the permission schemes and issue security schemes of your JIRA projects. Best regards, Peter

Hi Burcu, You could use the rest api and a script on another machine to simply call the rest api to create those issue every Monday. More information about the rest api can be found here: https://developer.atlassian.com/jiradev/api-reference/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-create-issue If you…

Hi Mark, Stash is an Enterprise BitBucket solution you can host yourself. It's more directed toward enterprises who want to use it behind their own firewalls but should serv you well also. And it integrates nicely with the other atlassian tools. Best regards, Peter

your welcome, I'm happy I could help :)

Hi Charles, You should submit your feature request here : https://jira.atlassian.com/ This is more a support community. Best regards, Peter

Hi Eslam, You could take a look at the script runner and it's escalation service : https://jamieechlin.atlassian.net/wiki/display/GRV/Escalation+Service Or you could try doing it using a jelly service that runs every minute and simply sends an email containing all issue from a certain filter (which you'll base on the SLA)…

Hi Hannah, You'll need to edit the default field configuration to make Resolution a non required field. Best regards, Peter

Elliot you could do something like this in JQL : priority changed TO Blocker ON "2013/12/04" maybe that could help you in generating a report? Best regards, Peter

Hi Elliot, You could take a look at the Service Desk Plugin for Jira, It has real time reports based on SLA's. And these SLA's will change when you change the priority. Take a look here : https://www.atlassian.com/software/jira/service-desk So you're SLA for blockers would be 10 days, as soon as an issue fullfills all…

Hi Whip, You could always create custom single select lists for each of your projects and use those to indicate the project custom priority. You could even combine this with the current Jira priority field to have both a global priority and a project priority. Best regards, Peter

Hi Pierre, I'm glad you could figure it out on your own. You are indeed correct: Jira will see that the Sprint has officially started at 8:00 in the morning and that you've added all stories only in the afternoon, which makes them scope changes. The solution is indeed to start your sprint after the sprint plannings…