Shawn Masters Expert

It usually is a permissions issue at that point. Make sure you have it so anyone in the group Jira-User can "Browse Projects" and "Create Issues"

You might be able to use "Automation for Jira" or one of the Scriptrunner addons to monitor for a change to the "sprints" field? Or perhaps move the issues in the sprint to a certain status when the sprint starts? 

You may have misread the permission; you can restrict "Browse Issue" by using "Issue Security Schemes" via Permissions there is a Browse Project permissions. Browse Project - view individual issues (except issues that have been restricted via issue-level security). Many other permissions are dependent on this permission,…

When you setup the Issue Security scheme via Admin > Issues > Issue Security Schemes you should have the option to set the default security value. When viewing the Security schemes if you select "edit" you can modify this value as well. You then apply this scheme to the project(s). 

JWME addon is able to do this fairly easily. Alternatively you could also use Automation For Jira addon 

They removed this at request of the community. On the cloud version, we do not have a way to modify this. On Server you can edit some code to change this. 

We were not able to find a way to pin point who starts a sprint....we ended up limiting permissions to users so only the Product manager/scrum master could start the sprints

Its part of "Key" column. If you remove "Key" you will see the issue ID also is not present. 

Dont think you can get more than 2 drop downs via custom fields in Jira Cloud. Jira server is more flexible and can prolly accomplish this via some edits. 

{color:#14892c} "INSERT TEXT HERE" {color}

We werent able to get it to work without hitting the entire Org as well. We ended up getting rid of the Orgs due to user complaints of spam mail. 

Id start with a system reindex. I saw several alerts this morning stating one of the Storage servers failed over and caused a plethora of connection issues...perhaps this is related? Considering that function is part of Jira Agile I would check to ensure the modules arent disabled and then raise a ticket with that group. 

You'll definitely need the mail handler or a registered email address to process incoming emails as Service Desk tickets. https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html#Receivingrequestsbyemail-Verifyyourlinkedemailaccount We use the Cloud email address and mail handlers to…

Did you remove the mail handlers access to the service desk? I believe the emails processed are seen as a system account not the actual user who submitted the email. 

Not quite the answer your looking for but we use labels on pages in the space, this works like meta for keyword searches and what not.

You can modify the "Issue Type" to call it Epic /Feature/etc. To have a kanban board focus on Epics only you can set a filter on the board to only look at those issue types. You can also use "Quick filters" to further filter the board while viewing it. Editing issue types:…

.... even with 0 quick filters you should atleast see the "QUICK FILTERS:" under the name of the board.....Do you have any addons modifying the boards that might be causing a conflict? Also are you on Cloud/Server?

I think you need to specify the worklog ID to get the expanded results

You would be better off converting the HTML to JSON or CSV format and using the External Importer built into Jira. 

As Nic mentioned below, JEMH is absolutely AMAZING for this and once you give it a try you will not regret having it installed in your instance. Alternatively, if you can get the workflow to generate the email without the issue key in the subject line, then Jira should process it as a new issue. 

Not sure if this will change the system events 9might need to contact Atlassian) but the settings below impact the rest of the Cloud instance when our previous had selected English(UK) instead of English (United States) Admin > System > General Config > Internationalization > indexing language / Default laguage

You'll have to contact the Dev. The only documentation found was on this page: https://github.com/allenta/gitlab-listener

Need a little more clarification on this.... Does the original issue already exist and someone is replying to a comment/notification and you want that reply to generate another ticket? 

We ran into this issue with Older browsers and out of data Java installs. Best rule of thumb is to grab the latest version of Chrome and see if the issue persists. 

I need it to be a bit more flexible. Since its a daily report I need the JQL to be able to show linked issues from that project somehow. something like, Project = X and linkedIssue in Project "Change Request" and Status != Closed

Thanks Cody

I would also like to see the same functionality Bill Cushard was requesting, were you able to find a resolution?

We utilize Tempo to do this. The timesheet function allows us to view a collection of their issues based on a time range. You can also accomplish this using filters in the Issue navigator, with the right syntax you could do this.

None of our post functions are working anymore either.....

We are also looking for this