Tarun Sapra Community Champion

Hello @Evelyne Bösch Labels is a free text field thus you should use the criteria of "project" in the board filter even if it means having issues from multiple projects. You can also have create sprint button active when you have the required permission in all the projects referred by the JQL filter of the board.

Thanks all for the reply, it's now working fine after reindex, and removing the listener and adding it again. 

Hello @Andy Heinzer Thanks for your response. Since I was trying this in last year feb thus I might not remember all details of the process but I clearly remember the following things * The remote link was not created, in the end I added the URL to the issue in the comments using commentManager. * The two Jira applications…

Yes, I re-index the complete system and would try these approaches again. It generally works well for other custom fields, but for this custom field it's just not working. 

Hello I tried the approach of issueManager plus the explicit reindex code but that didn't work as well. 

Thanks for the response, but I don't see anything in the logs.

Hello @Rangaraj The cloud version is always the latest version, thus in order to restore your cloud backup on the server then you need to make sure that the server version is the latest as well. Complete docs here…

Hello @Nikhil Currently, Jira doesn't support cloning an issue into another project. You can "move" the issue in another project and in the destination project you can have the field hidden in the field configuration. I personally use "Clone plus" plugin for all the cloning operations as out of the box Jira doesn't provide…

Hello @[deleted] I don't think a plugin is required for the second point as this kind of automation is supported out of the box in JSD https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-allow-customer-close-reopen-issue/qaq-p/67487…

And for your 2nd requirement, you can do this out of the box using Automation rule provided by Jira service desk https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html?_ga=2.43484195.746291664.1548063624-1359772982.1527518782#Automatingyourservicedesk-Setuparule…

Hello @Bhanu Chander Regarding the pausing the resolution, have you read the docs, as it's nicely defined in the docs https://confluence.atlassian.com/servicedeskcloud/setting-up-slas-732528967.html#SettingupSLAs-Setatimemetric

Hello @Olivera Tancheva Have you imported all the classes like "InvalidInputException" Can you paste the screenshot of the complete validator here. And as Nic said, also add some logging.

Hello @Bogdan Kulish I would suggest you to read the permission documentation from tempo to get started and grant users the right permissions. https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785879/Granting+permission+to+users

Hello @Mouli As @Alexey Matveev has already mentioned that the epic panel already has the sum of the story points of the child issues. You can also use Portfolio plugin, which sums up the story points of the epics and provides the aggregated points at the epic level. Along with details like "original estimate" and current…

Hello @Priyanka Karguppikar You will have to add the custom fields on the edit screen as you want them to be read-only only after certain status and not for all statuses. In this case you can write a script in behaviour in which make the field in read-only mode for a group of statuses that come after the status "a". You…

Zephyr enterprise seems to provide support for REST API, but if you have Zephyr as add-on then i guess the only way right now is through another add-on of theirs which is ZAPI. https://marketplace.atlassian.com/apps/1211674/zapi?hosting=server&tab=overview

Hello @Priyanka Karguppikar To make a field read-only you would need to use Behaviour module of the script runner plugin. In the "initializer" section of the behaviour you can add the condition to make the field read-only for certain statuses. Plenty of samples here…

There is a paid plugin for it https://marketplace.atlassian.com/apps/23216/field-security-plugin-for-jira?hosting=server&tab=overview But it seems to support only custom fields

Hello @Freek Swart Field level permission are not supported yet in Jira. https://jira.atlassian.com/browse/JRASERVER-1330

Hello @oferrer What you want is a very popular requirement. And the good thing is that Jira has finally implemented it out of the box in Jira 8.0 (currently in beta) . Thus you don't need any plugin for it as it will be supported out of the box in 8.0…

Hello @Eric Roetenberg Out of the box it's not possible on Jira cloud to extract this information, you could try an cloud addon for achieving your requirement. https://marketplace.atlassian.com/apps/891368/xporter-export-issues-from-jira?hosting=cloud&tab=overview

The above JQL fetches issues from all projects starting with "productname"

Hello @Stefan Regex for projects is not supported by default in Jira. But by using a paid plugin (Script runner) it's possible to have it. See here https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_projectmatch_componentmatch_versionmatch project in projectMatch("^Productname .*") 

Hello @Gregory Riccardi My suggestion to you is that you should use a custom field and populate the value of the transition in the custom field during post-function of that transition. And later you can use JQL to query on that custom field and see the issues pertaining to certain transitions.

Hello @Felix Lorenz If you are using next gen project in cloud, then you can use roadmap feature to add issues to epics. Currently you can't add issues of non-next gen projects to epics of next-gen projects.

Open request here https://jira.atlassian.com/browse/JRASERVER-67680

Hello @Felix Lorenz Currently, in Jira its not possible for an issue to have multiple parent epics.

@Nic Brough -Adaptavist- is correct, you don't need to explicitly cast the object. Though I personally always prefer to cast to the right object in order to have good readability of the code and since groovy is dynamic language thus not casting objects leads to complains from the IDE.

https://jira.atlassian.com/browse/JRASERVER-63833

It seems iPad is not currently officially supported https://jira.atlassian.com/browse/JRASERVER-34075