Tarun Sapra Community Champion

For stories, Epic link is exported as "Issue key" of the linked epic in my JIRA server version instead of epic name which is displayed on the stories when it's linked to epic Is this the issue which you are talking about?

ComponentManager has long been deprecated. Please use ComponentAccessor https://docs.atlassian.com/DAC/javadoc/jira/7.1.0-m01/reference/com/atlassian/jira/component/ComponentAccessor.html From Docs The ComponentManager also has various static accessor methods for non-Pico-managed objects,…

Currently it's an open issue - https://jira.atlassian.com/browse/JRASERVER-8426 Please see the KB article here -https://confluence.atlassian.com/jira/how-to-add-comments-to-excel-export-316113321.html You can also install "better excel" plugin which does this for you.

Please Read this - https://confluence.atlassian.com/jirakb/reconfigure-jira-by-running-the-setup-wizard-again-674988433.html And this part from the above link - From JIRA Home Directory, delete the dbconfig.xml file. If you wish to wipe off the data for the instance, drop the database as well. Thus, you can stop your jira.…

Currently it's an open ticket, here - https://jira.atlassian.com/browse/JSWSERVER-10762 (Create a dashboard gadget for the Velocity Chart) If you really need high quality reporting you might look into additional plugins like EazyBI or Arsenale Dataplane for JIRA.

Hello Shirish, Have you gone through this guide -https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html If you still have specific query you can directly contact Atlassian support here - https://support.atlassian.com/contact/#/ 

I am using JIRA 7.4.3 server version and it's working fine for me. In the CSV export of current fields I do see Epic name being exported. 

It's an open issue tracked here. https://jira.atlassian.com/browse/JSWSERVER-14746 Please see the comments, some people have suggested "Better excel plugin" . Otherwise you can make sure that Epic Name and Summary are same for the epic that way you won't miss the epic name field in the export.

Did it show an error at the end of installation? Has it installed an existing JIRA service which you can start/stop?

https://getsupport.atlassian.com/ 

Glad to know that it worked, please accept/upvote the answer. thanks.

Hello @Chris Lange You can try script runner as mentioned by Krisz as well. I would use the method "issuesInEpic:" https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_issuesinepics For removing stories from board which are connected to epic in status "open" "your current query" AND issueFunction not in…

Did you report about it to Atlassian support as well. As currently I can see arrows on the kanban board swim lanes @ jira cloud 

Yes indeed, the ordering is based on the order in the release page of the fixVersions.

Possible duplicate here - https://community.atlassian.com/t5/Answers-Developer-Questions/How-would-you-find-all-numerically-greater-Fix-Versions-WITHOUT/qaq-p/558897 And similar request here - https://jira.atlassian.com/browse/JRASERVER-61828 If your request has been addresses, please accept/upvote the answer. Thanks.

The issue which is done for JIRA porfolio is this one (JQL support for Multi level Parent Link) - https://jira.atlassian.com/browse/JPOSERVER-1883 For the cloud it's still an open issue - https://jira.atlassian.com/browse/JPOCLOUD-1883

Have you tried "fixVersion in versionMatch(<regex here>)"

Currently this is an open request - https://jira.atlassian.com/browse/CONFSERVER-31348 Hence you can display "issue links" in an column in jira macro but this will be links to other issues, but you can't display links to other pages in an column in jira issue macro.

Hello @FabienA "Fields Required (JSU)" is a feature of the JSU (JIRA Suite utility) . It's not supported out-of-box in JIRA thus either you should have the JSU plugin or a similar plugin for this feature to work.

Here are the docs - https://confluence.atlassian.com/adminjiraserver071/defining-a-screen-802592587.html 

It will be a global change when done in advance settings. There is an open ticket for storing user preference of comments order in the user profile - https://jira.atlassian.com/browse/JRASERVER-5443

You can write a JQL like assignee in membersOf("jira-developers") Here "jira-developers" group holds all the 16 members. If a group like this doesn't exist then you can create one. Just save the above JQL as a filter. Then on Dashboard use the 2 dimensional gadget and choose Y axis as assignee and X axis as "status" of the…

In both charts you will see this change reflected if the change is done during the sprint. If points are changed on the issue then in velocity chart "committed vs completed" will change with completed going up. And in the burndown chart you will see "scope" change 

Fields are added to Screens mapped to issueTypes. Now, if your "Epic screen scheme" is shared across all "Scrum based project" then adding the field tot he screen result will result in the field getting added for all projects. For the newly created scrum project. Make sure while creating the new project you *copy* the…

try this <your current jql filter condition> AND ("Epic Link" is not EMPTY OR type = epic) 

This generally happens if one of the tickets is in "closed" status which by default doesn't allow issues to be edited.

The field (dueDate) has to be present on the "create" or "edit" screen in order for you to enter the values. As per release notes. (if description in bold doesn't match your case then you will have to contact jira admin) Project level administration In JIRA Software 7.3, we allowed project administrators to edit their…

Are you doing a full system restore or trying to migrate projects from cloud to server. Have you gone through this guide? https://confluence.atlassian.com/adminjiraserver/migrating-from-jira-cloud-to-server-applications-938846963.html

Helle @[deleted] Chauhan , May be you can create a ticket in JIRA for the Atlassian team. As I am not sure if it's on their roadmap of features. 

complete docs - https://confluence.atlassian.com/adminjiraserver/configuring-workflow-triggers-938847513.html