Tarun Sapra Community Champion

PLease see here - https://confluence.atlassian.com/jiracore/blog/2015/07/search-jira-like-a-boss-with-jql You can easily do this by using JQL - > assignee = USERYYY and this should give you all the issues for that particular user.

Doing it in a post-function might be better than trying to do it in HTML/JS.

https://answers.atlassian.com/questions/211505/updating-a-custom-field-using-groovy-script-runner

You can create a board and add a swim lane something like fixVersion = earliestUnreleasedVersion()

anyone with any ideas?

yes i have project admin rights.

The customer need to have browse issue permission in the Product Enhancement Delivery to view the linked Epic's status only then they would be able to see it.

Make sure you have the right permissions. - https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-sprints/starting-a-sprint

Hi Ellen, I think you have given a very balanced opinion and I couldn't agree with you more when you say - "Please do your pricing fact checking on comparable solutions with HP or Microsoft or IBM or VersionOne or Rally or or or - all of which are bit piece solutions, compared to the full suite solutions provided by…

Did you add the commit trigger in the workflow? https://confluence.atlassian.com/adminjiraserver071/configuring-workflow-triggers-802592811.html#Configuringworkflowtriggers-Step2.Addatriggertoatransition

Get Crowd. It will save you from future mess that you can get yourself stuck into if your userbase grows and you still want to continue to use JIRA for user mgmt.

In this link - https://confluence.atlassian.com/adminjiraserver071/managing-project-permissions-802592442.html Follow the steps from "Creating the permission scheme" and once the scheme is ready you can map the scheme to the project, just remeber to give the respective groups "browse" permissions as there are lot of diff.…

You can create a group for each of the Client and put it's respective member in that group and grant "Browse" permissions in the project only to the corresponding group. i.e. for Client A -> group A -> Project A browse permissions and for Client B -> group B -> Project B browse permissions. The browse permission is part of…

You can create a group for each of the Client and put it's respective member in that group and grant "Browse" permissions in the project only to the corresponding group. i.e. for Client A -> group A -> Project A browse permissions and for Client B -> group B -> Project B browse permissions. The browse permission is part of…

For the whole of JIRA you can use the "GLobal Permissions" in the admin section and for individual projects you can use the "Permissions" section in the project "summary" admin section.

Especially if someone uses the term "application" that kind of has an implicit connotation of something independently deployable 

Yes, I have been working with Atlassian tools for quite some time and this really confused me, will be nerve wrecking for beginners.

Thanks Nic, now it's clear. I see the option of "JIRA Service Desk" trial in the manage application section. So I guess it will download the obr file and install it automatically or I can do the same manually from here…

Yes, Indeed. I do know about JIRA software using JIRA core since I also manage JIRA Software at a client. But in this case what's the best possible way to install JSD on the existing JIRA software application as the plugin option is no longer present.

Hello Nic, Isn't JSD a separate application altogether i.e. no longer a plugin. It can be integrated via application link with JIRA software https://www.atlassian.com/software/jira/service-desk/download

The code is for a particular issue but the question is for all the comments in the system made by a particular role.

Hi peter, it's written - Note that you can only delete a sprint if you have the 'Administer Projects' permission in all projects included in this board. The board only includes one project and the user has admin rights to that project.

All issues are from the very same project and yes they have schedule permissions. This issue is pretty perpexling as i have double-checked all the permissions.

All isues on the board are only from 1 project.

The same users also have Schedule permission.

there is no variable called "assignee" instead you need to do Dear <% out << issue.assigneeUser?.displayName %>,

Hi Jan, Make sure that your post-function is after the built-in "Creates the issue originally." post function, as it seems that you are executing the script which is using the "issue" variable even before the issue has been created.

Since you are using JIRA cloud thus I would request you to contact Atlassian support.

Hi, did you try basic authentication first? was that working?

Hi Edwin, Yes it's possible, you can use JIRA-Macro in confluence wherein you create a release notes page in confluence and write a JQL in the macro to import the issues pertaining to that particular Release and add relevant text. For example - having this JQL as part of the JIRA_Macro on the confluence page would import…