Tarun Sapra Community Champion

Ok, this is new for me, as I always thought that link can be accessed after the "create issue" event in the post-function

Hi Jamie, It could be the problem, but if the post function is at the end of all the post-functions in the create issue transition, wouldn't that qualify as a solution? Regards

Can you try getting the Epic issue ID from the Story's outward links? https://developer.atlassian.com/static/javadoc/jira/5.0.5/reference/com/atlassian/jira/issue/link/IssueLinkManager.html#getOutwardLinks(java.lang.Long) public List<IssueLink> getOutwardLinks (Long sourceIssueId)Get links from an…

Hi Giri, Just to add to Nic's asnwer. Kanban backlog is a new feature only available for JIRA cloud, you can read more about it here - https://confluence.atlassian.com/jirasoftwarecloud/using-your-kanban-backlog-856846180.html 

In the sub-task post-function you can access the parent issue as "sourceIssue" and then can display the key of the parent issue in the custom field of the sub-task.

By default it's unavailable in JIRA but using Script RUnner plugin you can get it to work https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions+With+Comments#ScriptedJQLFunctionsWithComments-hasComments([numberofcomments]) https://answers.atlassian.com/questions/232265

It's not an built-in function, rather it's from the Script Runner plugin, please make sure the plugin is enabled and if it's enabled then please enable/disable the module for this JQL function from the Manage Add ons sections. https://answers.atlassian.com/questions/173044

Hello Karrie, In JIRA you can toggle the transitions of workflow based on conditions but you can't toggle the workflow status. My suggestion to you is to use seprate issueTypes for customer and internal teams and then creation of customer requests leads to creation of linked issueTypes belonging to the team having a…

please accept/upvote the answer, if you find it satisfactory

Hello Kalpana, It's not possible in JIRA, you can only subscribe to groups. Atlassian has closed this particular feature suggestion - https://jira.atlassian.com/browse/JRA-9746

Indeed but there are certain issues like the one above and setting "default values for system fields" that really need attention.

It's been 13 years!

Currently, only JIRA admin can create issues, you can vote here - https://jira.atlassian.com/browse/JRA-1431

But i feel, atlassian should have a separate Agile board create permissions as it's tightly coupled to other stuff which is just so "uncool"! Create Shared Objects Permission to share a filter or dashboard globally or with groups of users. Also used to control who can create a JIRA Agile board.

from the docs - Before you begin, please note that you will need the JIRA 'Create Shared Objects' global permission before you can create a board.

https://www.youtube.com/watch?v=CkOKjo8aJEA

Could you please accept/upvote the answer. thanks.

You can't do it without a plugin/add-ons, it's a open request in JIRA 's JIRA - https://jira.atlassian.com/browse/JRA-5225 With add-ons like Script Runner it's piece of cake and via WF post-functions which you don't intend on using.

Version report is required to know the number of issues related to that particular version and it's related to the scrum board - https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-version-report how will you know something like that through Jenkins?

The filters only work on the issues fetched by the main JQL filter, if that filter isn't fetching any XYZ issues then nothing would work, but if your board's core filter is fetching issues from both project then you can use quick filter to fetch issues only from XYZ project these issues would be sub-set of the total issues…

Make sure you check the things stated in these two links - https://answers.atlassian.com/questions/279188https://confluence.atlassian.com/display/AGILEKB/Can%27t+See+Issues+in+Kanban+Board

Disable the fish-eye plugin in the manage addons plugin admin page.

SELECTu.user_name,u.first_name,u.last_name,u.email_address,d.directory_name fromcwd_user u joincwd_directory d onu.directory_id = d.id whereu.active = 0;

Your instance's total memory is very low, from the docs ( I feel it should always be atleast 2 GB) For a small number of projects (less or equal to 100) with 1,000 to 5,000 issues in total and about 100-200 users, a recent server (multicore CPU) with 2GB of available RAM and a reasonably fast hard drive (7200 rpm or…

It's not working because of this - https://confluence.atlassian.com/jirakb/html-code-appears-in-description-fields-779160717.html better to use wiki-markup - https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

There is no limit on project and components. In JIRA you can't link projects, thus the best approach is to have components for smaller initiatives, and create a board (Scrum/kanban) wherein you fetch issues from multiple components. What do you mean by "but lose the release versions for that…

Hi Amber, Any new updates about Stash- JIRA integration as I am currently evaluating Stash, but I don't see major benefits of Stash over jira-github integration.

Hi , Any new updates about Stash- JIRA integration as I am currently evaluating Stash, but I don't see major benefits of Stash over jira-github integration.

it's a network firewall issue which is causing SSO to act wierdly and we are working on it.

Yes SSO is enabled, our test environment is also using the same crowd. I tried to login without the checkbox ticked in the chrome incognito browser still no luck, i have to check the tickbox only then it works.