Tarun Sapra Community Champion

Please note, Jira core server doesn't have boards yet, the boards feature is only part of Jira core cloud. So if you are going for on-premise installation of Jira core you *will not* get boards Please see this open request https://jira.atlassian.com/browse/JRASERVER-45690

Hello @ABoerio Even if yours team is not an Software dev team still you can benefit from the Jira Confluence setup. Both of these amazing tools offer loads of features useful even for non-software teams. Jira core cloud does offer boards which you can use See here…

Duplicate https://community.atlassian.com/t5/Jira-Service-Desk-questions/Reporting-in-Jira-service-desk-and-export-to-predefined-PDF-Form/qaq-p/900788#M20878

Hello @Pooja There is a paid plugin for customized PDF reports https://marketplace.atlassian.com/apps/5167/better-pdf-exporter-for-jira-pdf-view?hosting=server&tab=overview Once you install it then you can install the below free app to send scheduled PDF reports to all stakeholders in customized format…

Hello @tanhm2 Burndown gives you all the info for the single sprint, when you want the same information, then you need to do some customization for achieving similar requests. Based on the reports I have shared with you in above links, you would need to write your own JQL filters which get you issues which were…

Basically beats framework is being used to feed logstash which transforms the data and feed it to the Elastic cluster and Kibana then displays the charts which you can easily configure.

Hello @Graham Horsman There was a talk this year at the Atlassian summit discussing the architecture of ELK with Atlassian apps. Here's the link https://www.youtube.com/watch?v=SQ2pyS6aTpM It contains most of the architecture and setup related info which you need.

Cloud is sometimes offline and also most of the great plugins (Apps) don't offer all their features on the cloud. On premise is a really good option, but if you want to stay on cloud and don't want to manage the Infra and other stuff yourself then best option is to use "On premise on AWS cloud" this way you don't have to…

Hello @tanhm2 Your requirement can be implemented in Jira. But it's not supported out of the box. If you intend to create reports across sprints and also based on aggregation of estimation (story points or time) across data range or for a fixVersion(based on releases) and then display them, then you need a plugin for it…

Cloud is not operation right now, that's what the link clearly says

https://status.atlassian.com/

Yes, cloud is giving errors for some customers. Please track the status here https://status.atlassian.com/

Hello @d-sokolovskiy This feature is now supported out of the box https://scriptrunner.adaptavist.com/5.4.28/jira/releases/current-release.html * [SRJIRA-2668] - Add a Script Fields Template for Dates without timestamps

It's supported out of the box now https://productsupport.adaptavist.com/browse/SRJIRA-2668 https://scriptrunner.adaptavist.com/5.4.28/jira/releases/current-release.html

Tempo reports part of tempo timesheets provides all the information you need.

Hello @Joe Charman It should be straightforward, you can get the base URL using def baseurl = com.atlassian.jira.component.ComponentAccessor.getApplicationProperties().getString("jira.baseurl") Just append the following to the base_url complete_URL = base_url + "/browse/" + ${issue.key} complete URL is the final URL which…

Hello @Alexander Along with the changes which I have shared already, just change your code from def assignee = issue.getAssigneeId() to def assignee = issue.getAssignee() And it should work

Glad to know @Alexander that it works, please accept/upvote the answer so that others are helped as well. 

Then you should save the ApplicationUser object instead of string in the custom field updateValue.

Hello @Alexander What's the type of the field "technolog" in jira, is it text or single select etc

Hello @Nick You have to import the component accessor class as well https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/component/ComponentAccessor.html Add this in your code in starting of the class import com.atlassian.jira.component.ComponentAccessor

For having sub-ticks under parent tickets, you would need to have swimlanes per stories, in this way the child tasks will be listed under the stories.

Hello @Alexander This is not right in your code def value_a = technolog.getValue(issue) To get the customfield value you should use issue.getCustomFieldValue def value_a = issue.getCustomFieldValue(technolog) Also, to update issues you should always use IssueService…

Hello @Sibylle Glad to know that it's working, could you please accept/upvote the answer so that others are helped as well.

Hello @[deleted] You should have added the "sub-task" field only and only in the backlog section of the "card layout" configuration section, I think you have added it in the "Active Sprints" section and thus you see it twice. 

Hello @Sibylle It's working fine for me in 7.10.2 version of Jira. I have swimlanes in Kanban board configured as per assignee and sub-tasks is in it's own lane and parent task is in a different lane as both of of them have different assignee. And each assignee has it's own lane and own set of issues.

Hello @[deleted] Could you please elaborate on the problem with some screenshots, because in the Kanban backlog its possible to see the sub-tasks under the parent story. In the Scrum Backlog it's not possible to see the child-sub-tassk but what you can do is to add the "sub-task" field in the card layout of the backlog…

Hello @Nick The approach suggested by @Orkun Gedik is useful for newly added issues in comments, but not if you want to link issues which are already added in the comments. Because the listener will be triggered based on the event MentionIssueCommentEvent only for new scenarios and not for existing tickets if you wish to…

Hello @Sudheer Kumar Vempala Can you please share the business reason behind your requirement, i.e. you want to hide the fields on the issue screens but you still want to populate them with values? Also an hidden field should be present on view screen, it's not required at all on the create en edit screen.