Tarun Sapra Community Champion

You have to use script runner plugin for searching for partial text (regex) as JIRA doesn't support it out of box thus "summary ~"\\[XXX\\] "" won't work in JQL as partial text search isn't supported by JIRA, rather use script runner plugin as provided in the links below.

Are you entering the correct board name as you have to just enter the board name and whats "AA , BB, CC, DD" . What kind of naming is this? Also please validate in the board that you have an closed sprint in the board as the "previousSprint" returns issues from last closed sprint.

This JQL can be sent as "Subscription" email to students

duedate > 7d Will return all the issues wherein the "duedate" or whichever date field you want has a value greater than 7 days from the current day. I.e Event happening after 7 days. 

What is returned by issueFunction in previousSprint(<your board name here>)

https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_completeinsprint

The following function should be able to help you to previousSprint previousSprint(board name) Shows issues that are members of the last completed sprint.

This should be straightforward to implement You can use the built-in script listener "Fast track issue on transition" In this you can configure the listener to trigger it for the "issue commented" event for a specific project. Based on the condition (Approve or Reject) you will need to add 2 listeners which fire two…

My suggestion is to contact the Atlassian support about this matter. https://support.atlassian.com/

Also, while create issues. On the create issue popup on the top right, there is an option of "Configure fields" when you click on "configure fields" then you can click on the link "Where is my field?" and then type the field name - "Story points" in this case and JIRA will also tell you exactly why the field is not…

https://confluence.atlassian.com/adminjiracloud/associating-screen-and-issue-operation-mappings-with-an-issue-type-776636504.html

You need to also add the Story points field on the "Screen scheme" associated with the issue in the project's screen scheme.

Empty custom fields are not displayed on the issue view screen. Ability to choose whether to show the empty field or not is an open request in Atlassian's jira. See link here - https://jira.atlassian.com/browse/JRASERVER-2997 

Adding a collaborator to a service desk * In the service desk, go to the People tab > Collaborators section. Click Add collaborator. * Follow the prompts, search for the user you want to add and then add the user to your service desk. If you cannot find the user from the search, it means that the user does not have a user…

You need to add your "JIRA software" users in the "Collaborator role" From the docs - Collaboratorsthe Service Desk Collaborators role Collaborator can: * View issues, comments and attachments * Add attachments and delete their own attachments * Add internal comments to issues and delete their own comments * Watch and vote…

If you have script runner plugin installed then you can write a script which uses "CommentManager" to iterate over the issue comments and update the custom field object with the comment's value.

https://jira.atlassian.com/browse/JSWSERVER-5200 

I am afraid this has to do with card size. Because in order to display the complete summary the card size needs to be increased. Card size customization is an open request.

Also, in the project have you mapped the project with the project's field configuration scheme?

Can you paste the screenshot of the project's "Field configuration scheme" ? https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html

JIRA provides good information about why some fields are missing. You can always runt hat check. On the create screen pop-up on the top right there is an option of "Configure fields" you can click on that option and then click on the link "Where is my field?" and then enter the name of the missing field and JIRA will…

Hello Dov, Make sure that the IssueType screen scheme for the project contains proper mapping for the bug issueType thus there is a "Bug screen scheme" having the "Kanban Bug screen" for the create/edit/view operations. Also, it's not a good idea to map custom fields to global "all issuetypes" contexts. Regards, Tarun

I have personally used "Dataplane Arsenale" reporting add-on and it's quite good. Though it's not a traditional BI tool but creates excellent reports which can be customized and can be embedded on the dashboard and confluence pages.

Possible duplicate with probable answers - https://community.atlassian.com/t5/Jira-questions/Workflow-Transition-in-Jira-How-to-allow-all-statuses-except-one/qaq-p/10192 

the users can be part of a specific groups

You can use charts like "Average number of times in status" and "Average time in status" on the search results of JQL like status changed FROM "open" TO "in progress" BY membersOf("jira-administrators") 

Try the "Workflow report" feature of the "Better Excel plugin". It exports the transition times in an excel format.

Filter results gadget can be used and you can mention the issue using JQL parent = "EV-151" And this will list all the sub-tasks of the issue and use this JQL filter in the filter results gadget on the dashboard. 

Use the JIRA macro in confluence and in the macro use the JQL query parent = "EV-151" This will list all the sub-tasks of the issue in confluence. 

Here's the sample code - https://scriptrunner.adaptavist.com/4.3.6/jira/recipes/misc/running-a-jql-query.html The searchresults should be nil for validator to be true.