Peter Van de Voorde Community Champion

Hi Pawel, Take a look at the documentation here: https://confluence.atlassian.com/display/JIRA/Running+JIRA+as+a+Service Best regards, Peter

Hi Marcel, I don't think there is a quick solution for your problem. It's not possible to see the usage of a custom field through the web interface. It will probably be possible with some queries in the database. Best regards, Peter

Hi, You'll need to use conditions on your transitions to do what you seems to be wanting, take a look here to learn more about it: https://confluence.atlassian.com/display/JIRA/Advanced+workflow+configuration Best regards, Peter

Hi, Simply give them Transition issue and Resolve issue permissions but not the close issue permissions. Best regards, Peter

Tarun, Does your user have project administrator rights for all projects? As explained here : https://confluence.atlassian.com/display/AGILE/Deleting+a+Sprint ? Best regards, Peter

Hi Tarum, Do they have schedule permissions for each project from which issues are included in your sprint? Best regards, Peter

Hi nathaniel, You'll need to contact atlassian support directly for this: https://support.atlassian.com. This is just a community of users and experts we can't really help you with this. Good luck. Peter

Hi Gunther, I would post a support request here : https://support.atlassian.combecause you're on an OnDemand instance they are the only ones that can take a look in the logfiles to see what went wrong. Best regards, Peter

Hi Chris, Can't your approver simply assign it to the worker? I suppose they will know who's who in this kind of setup. It will be less messy than forcing it to automate. Best regards, Peter

Hi Piotr, In the latest versions of Jira Agile the way Sprints work has been changed. An issue can now only be part of one sprint. So if this issue is visible on several boards the sprint it's in will also be visible on all those boards. It can no longer be part of a different sprint on each board. Best regards, Peter

Did you setup trusted communciation between JIRA and Confluence? https://confluence.atlassian.com/display/DOC/Setting+Up+Trusted+Communication+between+JIRA+and+Confluence Best regards, Peter

Hi Rob, You could try using javascript in the announcement banner so it only shows up when the browser is IE. But as I don't have any decent javascript experience I wouldn't have a clue about which javascript you need exactly. I did find the following question that might help you on your way:…

hi Zhe You'll need to log a ticket at https://support.atlassian.com they can help you, this is more a forum for the community not the Atlassian support desk. best regards, Peter

Johannes, Don't delete the thread, simply mark your question as answered by selecting your answer as the correct one. Best regards, Peter

Hi Johannes, What are you exporting? An issue list? How are you exporting it exactly? Which version of Jira do you have installed? Best regards, Peter

Hi Dan, I recently had the same issue, it seemed that some of my users were found twice in the people directory which caused a whole stacktrace in my log file and not finding them using the @mention macro. I resolved it by following the information here:…

Hi Adam, In this pages it's explained that what you are seeing in the file structure is the normal behaviour : https://confluence.atlassian.com/display/JIRA/Editing+a+Project+Key The attachment folder will keep the old project key. It's not correct that the links break. Is GASP the new or the old project key? And how…

Hi Adam, Is there an error in the log files that might explain what's going on? Best regards, Peter

Hi Andrea, You could do something like this : resolution changed AFTER -12w by "John Smith" which will give you all the issue for which John Smith changed the resolution in the last 12 weeks. Best regards, Peter

Hi Héctor, You should probably also use Crowd for SSO and User Management across your different applications. Your server distribution is a good idea, you could put Crowd on a separate server, but that's not really necessary (it could also share a server with Stash for example). If your clients don't have access to your…

Hi Tobias, Jira Agile supports both Scrum and Kanban out of the box and you can completely modify your worklfow, permissions and issue types in Jira. So could you please be a bit more specific about which agile processes and tools aren't supported in Jira Agile and you would like to have implemented? Best regards, Peter

Yes, You can just Select manage filters (in the dropdown menu next to the Issues in the top navigation bar) there you can share it. Best regards, Peter

Hi Shiva, It's not possible to assign an issue to a group. The whole idea behind assignee is that one person is responsible for the ticket. Best regards, Peter

Hi Abinaya, The Plan tab is always available if you use a scrum board (which you are if you are using sprints). More information about how to configure your board (and the quick filters) can be found here : https://confluence.atlassian.com/display/AGILE/Configuring+a+Board and in the link provided by Silviu. Best regards,…

Hi Abinaya, I think you should be able to see this in the History (History tab in the detail view) of the issue, I don't know how you can see this in the planning view unless you use a filter which contains all the stories that used to be in the previous sprint, that might help. Best regards, Peter

Hi Silviu, As the future sprint hasn't been started yet it can still be considered the top of the product backlog, but you are correct in saying that in the event that there are already some future sprints defined that the story will be put into the backlog of the upper most sprint on the planning screen. Best regards,…

Hi Abinaya, If the Stories are not completed at the end of a sprint (when you close the sprint) they will be moved back to the top of your product backlog. You can then just drag them into your new Sprint. Best regards, Peter

Maybe you can raise a ticket about it here : https://jira.atlassian.com ? Best regards, Peter

Hi Heiko, I think mergeinfo isn't supported by any subversion repo older than version 1.5. So you'll probably need to upgrade the repository. Best regards, Peter

Hi, If your configurations are identical (plugins, versions, ...) you could simply do an export from your production server and an import the problematic project into your staging server. This can all be done through the system administration pages of JIRA. You could also export the issues to excell, transform it into a…