Tarun Sapra Community Champion

Have you tested the compability of the plugin on a test instance running JIRA 6.2?

and here - https://confluence.atlassian.com/jirasoftwarecloud/customizing-cards-764478020.html (Card layout)

Yes, it's possible, you can do that in Card Layout section when you configure the Board. http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/

Please contact your network administrator to fix your firewall settings

The JIRA project which are underneath the boards have permission schemes. And based on those project schemes you can also manage permissions to the boards created from those projects. Project permission schemes - https://confluence.atlassian.com/adminjiraserver071/managing-project-permissions-802592442.html

Thanks Jamie, my bad, by classpath I meant only putting it in the filesystem.

You can search for specific comments(Comments ~"test" and order by lastUpdated) ( but this approach doesn't give you last updated comment, as lastUpdated means any field, status or comment)

https://jira.atlassian.com/browse/STASH-2490 See the comment from Mark - https://jira.atlassian.com/browse/STASH-2490?focusedCommentId=440773&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-440773

Hi @Swapna Kumar Vemula [Zephyr], Why is this crucial piece of instruction missing in the documents? https://zephyrdocs.atlassian.net/wiki/display/ZFJ0300/Create+Tests For beginners it's hard to find why the test issueType isn't available in their create issue screen. Thus please update the documentation.

Can you try deleting indexes folder and then doing a re-indexing again instead of just re-indexing without first deleting.

Hi @Haisam Ido, There are two ways to import CSV in JIRA 1) Under the issues section - "Import issues from CSV" 2) Under external system import (requires admin rights) If you use the second option(admin rights) you will see fields like Status, Assignee, Resolution etc which are not available if you try to import via the…

Yes, it's possible, but it's not a good practice, especially if your JIRA instances might become large after some time. If you still want to have 2 separate instances the it's better to use Virtualization.

You can try this plugin https://marketplace.atlassian.com/plugins/net.bull.javamelody/cloud/overview and then use "was" operator in JQL and see the kind of reports the plugin generates.

The worst thing you can do to easily bog down a large JIRA instance is to use "WAS" operator in the JQL. But it's just the tip of iceberg, there are other things like low memory, not using SSD drives, slow network, too many issues in rapid-boards, using poorly designed plugin functions in JQL is a major cause of slow JIRA.

Jira should come up with something as this is a pretty common requirement, keeping the old custom field values and having new ones only for the new issues!

Do you really need such a view, because in large jira installations with many many users, this would take ages to load in the dashboard. as system dashboards are good examples of global views. I would stick to customized filters with relevant results and use JQL for more fine grained results using pie charts for users &…

Indeed Thanos, I am aware that return is optional, but I wanted to make sure that a boolean is returned as a single false might have been interpreted as a string, as I not aware of the exact behind the scene semantics of the code that kicks in when the validation is executed.…

Did you try "return false;" instead of just false.

I would suggest to use Script Runner in the post function to fetch the user from the role and then use script to update custom field value with the username import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.security.roles.ProjectRoleManagerimport com.atlassian.jira.user.ApplicationUsersdef…

You can achieve it using JIRA built-in filter subscription functionality, please read here - https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html

Ok, Please upvote/accept the answer if it works out for you, thanks.

If there are no plugin, then default assignee can be based on "Component Lead" being the default assignee but you would need to use that specific component in your issue. But in your case you want it to be assigned to the "business owner", thus you have to select the component which has the component lead the business…

Do you have some plugins installed, as the functionality you want requires a plugin.

You can set default text for the custom field, is that what you require? https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field#ConfiguringaCustomField-default_valueDefaultvalue

please upvote/accept answer. thanks.

Here's you solution - please check your JIRA version and the version of JIRA which has this issue fixed https://jira.atlassian.com/browse/JSW-12016

I see another option - "Manage user status locally" , if I "untick" this option then would that mean that if the user is disabled in LDAP then it will be deactivated in crowd as well, which is something I actually desire.

Yes, the errors because of bad CSV, I can see locally row 66, 67 , 68 are all malformed thus the errors. Once you fix those columns it will work like a breeze, please accept/upvote answer. Thanks

Ok, please try this now, Create an Empty project in JIRA called "Agile Maturity Matrix" with a proper Key and remove the columns "project type", project key and project name from CSV and import the issues in the existing project, that should work.

Currently you have a Typo in your CSV , it says - "Project Tpye" instead of "Type" it's "Tpye"