Peter Van de Voorde Community Champion

Hi Bernard, Go to your Screen Menu in the JIRA Administration pages (you can find it underneath the Issues tab) Simply find the Resolve issue screen and add the field. Best regards, Peter

Hi Vlad, You'll probably need the Tempo Timesheet plugin for that kind of information. Best regards, Peter

Hi Rahul You could use a Field Configuration Scheme to simply hide those fields in all projects that are associated with this field configuration. You can read more about the field configurations here : https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour Best regards, Peter

Hi Sanu, Did you change the name of your applications recently? That might cause the problem. You could simply recreate the applications links again and see if that solves the problem. Best regards, Peter

Hi Ulrika, The user should be able to see the name of the Project Leader when he/she clicks on the project summary page. The project leader should know how to add somebody to a project, or whom to ask. There is no way for them to see who the project admins are. Best regards, Peter

I have no idea, that's not realy my cup of tea.

You can try to use the Message Custom field from the Jira Toolkit Plugin (https://marketplace.atlassian.com/plugins/com.atlassian.jira.toolkit ) But you can not place this field above the project label. Maybe you can change the css of the create screen?

Hi, I would simply restart your old JIRA instance and retry the export once more. It could simply have been a fluke. Best regards, Peter

Hi Debbie, maybe the answers over here could help you out? : https://answers.atlassian.com/questions/92908/is-there-any-way-to-create-a-form-in-confluence-and-save-the-inputted-data-to-a-page Best regards, Peter

Hi Gutro, Is this in OnDemand or your own hosted environment? Best regards, Peter

Hi Nick, You could use @Mentions for this kind of questions, you can find some more info about @Mentions here : http://blogs.atlassian.com/2013/06/using-watchers-and-mentions-effectively/ and here : https://confluence.atlassian.com/display/DOC/Using+Mentions Best regards, Peter

Hi Nick, This is not how this functionality works. The purpose is to simply inform the person about this issue and write an extra note why you share this issue with them. So it's not really a comment but more an extra clarification towards the person(s) you are sharing the issue with. So it's not possible to add your note…

It was the advanced one :) No statusses are mentioned in this query, which means all should be included. could you please check if your project truly has the correct workflow? maybe you didn't publish the draft? Best regards, Peter

Hi flip, could you copy and paste the filter text in here? Best regards, Peter

Hi Flip, Is the filter behind your Kanban Board based on certain Statusses? If your new one is not included in the filter it will not be shown on the board. Best regards, Peter

Hi Trupti In the History of your issue you can see all the changes that are made and the timestamp at which they were made, does that help? Best Regards, Peter

Hi Sven,Maybe this article can help you out: http://stackoverflow.com/questions/16110528/tomcat-multiple-instances-simultaneously ?Best regards,Peter

Peter and Sven,It seems that your JIRA instance is locked, could you please follow the instructions here:https://confluence.atlassian.com/pages/viewpage.action?pageId=223220062

Could you take a look in the atlassian-jira.log file in the home-dir/logs directory of your second instance?If you have installed a second standalone the container shouldn't be an issue.Best regards,Peter

Hi Sven and Peter, What's the error message you are getting? I can't seem to see it in the attached screenshot. Anyway, if you want to install multiple instances of Stand Alone JIRA on a server you will need to change at least: * the ports the JIRA instances are using * make sure they use a different database * make sure…

Ok, I couldn't test it so I didn't know. Maybe you can take a look at the Script Runner plugin and the following thread : https://answers.atlassian.com/questions/49347/make-issue-link-a-required-field-is-not-being-enforced You can find the Script Runner plugin here :…

Hi Ananda, You could make the issue field required using a workflow validator. The JIRA Suite Utilities plugin has this kind of validator : https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities Best regards, Peter

Task is probably the default issue type in the Issue Type Scheme for this project. Or maybe the Epic issue is missing all together as Nic suggests. More information about Issue Type Schemes can be found here: https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects Cheers, Peter

Hi Albert, Currently this is indeed not possible with the Rapid Agile Boards. You could use quick filters and swimlanes based on queries to see which stories are in which epics and fix versions. Best regards, Peter

Or just put all the people in your System Admininstrator AD group also in your jira-users group :)

George, This isn't part of the standard Jira installation, it's part of the JIRA Suite Utilities. You might create an issue about it here : https://jsutil.atlassian.net/browse/JSUTIL You could also use the comment required validator that's part of this plugin :…

George, Might it be that you have a custom field called Comment? That could cause confusion and might explain this problem. best regards Peter

Hellen, Maybe you could ask Atlassian support if they can't change the max results to a larger number for your instance? You can request it here: https://support.atlassian.com Best regards, Peter

Hi Helen, It's a solution but not a really great one. Best regards, Peter

Hi Helen, This plugin could help you out: https://marketplace.atlassian.com/plugins/com.midori.confluence.plugin.archiving But it seems you're on OnDemand and not on a Hosted version. I don't about any other option. Best regards, Peter