Matheus Fernandes Atlassian Team

Hi, You can disable this for all users by disabling the system plugin. You can see how to disable this in the latest versions of JIRA in the following knowledge base article: https://confluence.atlassian.com/x/4QKpE Cheers, Matheus Fernandes

Hi Jayant, You could simply import a CSV file like: Summary, Select List Values, Other Custom FieldTo be deleted 1, Value 1, Other value 1To be deleted 2, Value 2, Other value 2To be deleted 3, Value 3, And when importing, point those columns to the custom fields. Just be sure not to map those values to existing ones when…

Hey there, The product is actually the same, the difference is the installation method. Version 6.3.6a has a simpler installation method whereas the 'Try JIRA' blue button while you're installing the product will install the product for evaluation, setting up all application properties and the database (HSQLDB)…

Hi, Jonathan. For JIRA and Confluence it is possible to achieve this, albeit it won't be possible to configure this (in the application side) for FishEye/Crucible. Please allow me to share below the steps to achieve this in each of those, as well as explain why this won't be possible for FeCru. JIRA In JIRA this is the…

Does it happen when using different browsers? And could try attaching the screenshots again? :P

Hi, Matthew. Yes, the JIRA backup is a zip file containing these two files. It is basically an export of the database to these two XML files, that can be imported using JIRA. As you noticed and Arthur also mentioned, it won't include actual configuration files or attachments, so please do backup the JIRA Home folder as…

Nice! You are welcome, Jig. :)

Sorry, regarding your question. Type: class Class: com.googlecode.jsu.workflow.function.UpdateIssueCustomFieldPostFunction Arguments: field.value = %%CURRENT_USER%% field.name = customfield_10731 This information is stored in the workflow's XML I've mentioned. :)

Hi Jig, Rather than editing the custom field's ID, I think you can edit the workflow's XML instead and either remove the post-function or edit it to "customfield_otherID". select * from jiraworkflows where workflowname = 'YOUR WORKFLOW NAME'; Copy the descriptor column to a text editor and edit the workflow as you need.…

Hi Alex, Unfortunately this is not possible in JIRA. There are actually two feature requests for it (and something similar), but that possibly won't be implemented anytime soon: * It should be possible to choose which issue type scheme is used by default * Remove Issue Types from the Default Issue Type Scheme Cheers,…

I imagine the Behaviours Plugin may help. If it doesn't though, I believe JavaScript in the field's description would be the best way to achieve this.

You can also simply copy the link of the Edit button instead of opening the page source. :)

Karie, If you navigate to your Project list in the Administration, you can find the Project ID (pid) in the URL of the 'Edit' button. (http://yourjira.com/secure/project/ViewProjects.jspa) Alternatively, you can select * from project in the JIRA database.

You are welcome! And no "duh" at all, Firefox and Chrome disable this plugin by default. (-:

Susan, This is probably happening because the Java plugin is disabled by default in Firefox and Chorme. Try accessing your Firefox » Add-ons » Plugins page and enabling Java TM... there to see if this will fix this issue. :) Cheers, Matheus Fernandes

You can possibly use WebHooks for this, see: Managing Webhooks.

To change the email subject to the way it was on the old versions, you'll need to add '<tt>$eventTypeName: </tt>' in the beginning of the <tt>.vm</tt> files inside the <tt>$JIRA_INSTALL</tt><tt>/atlassian-jira/WEB-INF/classes/templates/email/subject</tt> directory. Please note that you'll also need to restart JIRA after…

Milap, Could you actually describe a little better or exemplify what you mean by broken view? Thanks

You can possibly use a transition that has a post function to clear the resoltion, I think. :)

Ethan, It seems to me there's a post-function in the 'Create Issue' transition of the workflow being used by this project - see Editing the Workflow Transition for Issue Creation. This may be related to the second problem you described - the 'Resolved Date' is set when the resolution of the issue is changed instead of when…

Yeah, JIRA uses indexes so it will provide faster searches with a minor performance impact. But if the indexes are out of date.... :P

Also, when editing an issue in JIRA, the issue is automatically indexed, hence it would then appear in the issue navigator. ;)

Hello, It sound as the JIRA indexes got messed up after you renamed the fields, and it appears you've not re-index after doing so. If making any changes in any of the following areas, it is advised to re-index JIRA to avoid these kind of problems: * Field Configuration Schemes * Custom Fields * Plugins * Time Tracking See:…

Hi John, Currently, there is the Marvelution JIRA Hudson Integration integration project available in the Atlassian MarketPlace, which offers three plugins. From the plugin's page in the marketplace: The Jira plugin; providing all the Gadgets and Tab Panels and the ability to administer the Hudson servers and associations…

Kevin, It seems there's possibly a misconfiguration in JIRA's settings or your proxy's. Have you added the proxyName and proxyPort settings to the HTTP(S) connector in JIRA's server.xml file?

Hi Jay, It seems you are facing a known GreenHopper bug: GHS-5502 In order to avoid this error you will need to disable the GreenHopper plugin's feedback configuration. To do so you can follow the steps below: * Go to <tt>Administration » Plugins » Plugins</tt> * When the plugins page appears, click on the <tt>Manage…

If your project was created together with a board via the GreenHopper 'Getting Started' page, it will probably use a simplified workflow that: * has three default steps for Scrum boards: To Do, In Progress, Done. Or, * has four default steps for Kanban boards: Backlog, Selected for Development, In Progress, Done. However,…

Hi Erik, Could you tell us what happens when you try those filters? What is wrong with the output? I imagine you'd need to try adding 'or sprint is empty' to your query: project = 'projectname' AND (Sprint not in ("Sprint Name") or Sprint is EMPTY) Let me know if this helps!

Hi Alex, Try reverting the change so you can start JIRA, but if possible attach here the setenv file that wasn't working so we can take a look.

I'm glad to hear that. :)