Matheus Fernandes Atlassian Team

Hi, Sudhir. I don't think the stack trace you attached has much to do with the problem as that is regarding emails. Perhaps using the Development Tool in Chrome or Firefox may help diagnose this better. A good test would be to try putting JIRA in safe-mode to ensure this is not being caused by any add-ons. Cheers, Matheus 

can they search for the dashboard? (Dashboard top menu » Manage Dashboards » Search)

Please try checking the import logs which should provide further information regarding this. Also, try making sure that the users joad and rho1 for example have the Create Issues project permission before importing. :)

I'd say this is most likely related either to file system permissions (for example if JIRA was started with a different user from which it was installed), or due to core plugins being disabled. Still, I'd advise you to reach out to our support on support.atlassian.com. Just attach a support zip file as well as the output…

I have never used it. Perhaps the https://eazybi.com/help/jira link may help. Also, you can try a live demo on https://eazybi.com/accounts/1632/dashboards/test or see a demo video on https://www.youtube.com/watch?v=gc5Y3XdhKT4 :)

Dipti, I'm not sure, but perhaps the EazyBI add-on for JIRA can help: https://marketplace.atlassian.com/plugins/com.eazybi.jira.plugins.eazybi-jira

I think the JIRA Enterprise Mail Handler plugin can help you with this. :)

Hi Rabih, There isn't anyway to achieve this by default. Basically, JIRA reads an email and performs an action based on it, and this action will be the same as if the action was executed through the UI so JIRA cannot actually differ one from the other.

Hey there, Check the Properties on the Transition, and remove any jira.i18n.title or jira.i18n.submit properties from it. It's likely that the value specified there is not valid. Cheers, Matheus Fernandes

Anytime, and no worries, Marc. I'm glad to hear this is working for you. :) Have an awesome day

Marc, you should see the three buttons when seeing the list view of a filter you created under the columns menu: "My Defaults | Filter | System". Make sure that when editing the filter you're updating the "Filter" Columns, and when the user is vieweing the filter, it is also viewing the Filter columns rather than his own…

This will list you issues that have been reopened, but not necessarily that have been closed afterwards. :) As those are statements JIRA will understand them separately, so "status changed from resolved to open" may happen to issues where "status changed from open to resolved". Also, something like this would only work if…

Hi Rahul, You won't be able to find that by default through the database as you won't be able to "count" using the Issue Navigator. The following query should help you to find this in the database though: SELECT p.pkey||'-'||ji.issuenum AS "Project Key" FROM jiraissue ji JOIN project p ON p.id = ji.project WHERE ji.id IN…

Hi Shaakunthala, JIRA only creates rows in the customfieldvalue table when there is an actual value for the field. That is, it doesn't store fields with 'Null' values (e.g. if an issue does not have an Epic Colour, there will be no row referencing the issue/value on the database). That is the reason you see a difference…

Hi, Jirong. To edit the Sprint field in the closed issues, please just follow the Allow editing of Closed Issues guide. Please do note though that, as the Sprint is already active, those will count as scope changes. Cheers, Matheus 

Ken, do you mean the JIRA Timesheet Reports and Gadgets add-on? If so, it should be compatible as per https://marketplace.atlassian.com/plugins/jira-timesheet-plugin/versions

Just the one you change. There is an improvement request in JAC for users to be able to choose a default order: * https://jira.atlassian.com/browse/JRA-28290

Yes, you just need to click on the dropdown arrow on the right/top of the Attachments section and select 'Date':

Do you mean the Create Issue button in the top, or in the form itself?

hi there, Do you have to do it through JavaScript? Are you trying to condition it or something? You could always use the InProduct translation for JIRA plugin to "translate" Create Issue to Create Draft. Cheers

Duh, just go to Administration » General Configuration » Advanced and add '0' in the jira.comment.collapsing.minimum.hidden option in the newest versions. :)

Hi Long, I've been testing this here, and you can possibly do this by adding the following to the <tt>jira-config.properties</tt> file inside your <tt>$JIRA-Home</tt>: jira.comment.collapsing.minimum.hidden=0 You can see how to make this change in the docs below if you are not familiar with this file: * How to edit the…

Do you have any proxy in front of JIRA? And have you tried to run IE without the extensions?

Can you confirm if you have the JIRA Suite Utilities plugin installed? And, if so, can you ensure the version you have is compatible with JIRA 5.2.6? There is a known similar issue that is caused due to an incompatible version of the plugin, and you can see the KB for this here: https://confluence.atlassian.com/x/rgrSEQ

Hi Casuva, This is actually a recent bug that is being tracked here: JIRA interface is broken in Chrome v.22 Currently, the status of this bug is the following as per the bug report: We believe this issue is caused by a recent Chrome update. We expect that it will be fixed with the next version of Chrome. Given the time it…

You have two main options here to rename the username: * Searching and replacing in the XML backup - see Changing Usernames; * Use the third-party plugin Script Runner, which has a built-in function to rename usernames - Rename UserID; I hope this helps!

I'm glad to hear that! :)

The CLI is a tool by Bob swift that you'll need to download to use it - you just won't need to install it into JIRA as this is not a plugin (see the CLI docs). It is also possible to use a CSV file as you mentioned, you just need to create issues with it and associate a different (new) user to each issue. For example:…

Unfortunately not, the only other option I could find is the (kinda ugly) workaround described at 'How can certain jira fields be restricted from cloning' :(

I don't think this is possible by default, but you can possibly use the Clone Plus Plugin for JIRA from Bob Swift to achieve this. :)