Shawn Masters Expert

Additionally, you can add the users to an "Organisation" in Jira to grant them access to issues they didnt report but may pertain to them. 

Consumes 1 Jira USER license - not Jira Service Desk license. We have 4 dev teams that interface with our service desk (escalations and bug fixes raised by Tier 1 and 2 techs) 

Chrome / Firefox has been the go to for our user base (a few of the Mac users utilize Safari) We have seen some issues occur due to Extensions/addons in the browsers. Edge seems to work for the most part - see alot of quirks and issues when you get into Confluence. IE ....well we just plain refuse to use IE for anything if…

Tested this in my instance - no issues encountered. Verify file size vs Jira file size restriction Check Customer permissions (ex: if they arent a reporter or request participant in our instance the system blocks the attachment) 

https://community.atlassian.com/t5/Answers-Developer-Questions/Is-it-possible-to-change-Confluence-space-permissions-via/qaq-p/507131

Not required based on documentation https://confluence.atlassian.com/doc/supported-platforms-207488198.html

We have multiple platforms supported and had this same request. The PMs ended up getting together and building a Singular Portfolio to cover the year....this seems to have appeased the higher ups who were requesting this info. So now they have individual Portfolios they manage, and the Directors maintain an Overview…

Im not aware of any permissions or settings around Reporting in Jira Cloud. This may not be possible. 

Try removing colored text from the page. See if it works. I remember not too long ago atlassian reported an issue saving pages with colored text due to some syntax issue they were working on. 

https://confluence.atlassian.com/adminjiraserver078/backing-up-data-947189268.html

Remove the "Browse Project" from the permissions for all users (exclude site admin) OR Set Issue Security level to the project so that no one can access it 

https://confluence.atlassian.com/servicedesk025/managing-collaborators-754977407.html Take a look at the Collaborator permissions - they allow a user to comment/edit a ticket but not be assigned the work. This paired with Issue Security should accomplish this. 

Im not familiar with a "Text" mode. This sounds like a Chrome extension ....which may explain why only part of your user base is encountering the issue stated above. 

I would try other browsers. I tested Chrome on my own Mac (same versions) and had no issues. So it looks to be specific to you. 

Have you found anything to manage Budgets and Portfolios? Tempo has a nice idea....but they keep dragging their butts on releasing a working product to Jira Cloud. 

'link to a bar' - clarification needed You should be able to include external links with no issues (depending on what your goal is) 

We accomplish this by using the following addon (they have a free version 'Lite' as well with limited functions) https://marketplace.atlassian.com/plugins/com.codebarrel.addons.automation/cloud/overview

What version of Jira? Any addons installed to modify workflows? Most current documents for Cloud/Server found here: https://confluence.atlassian.com/adminjiracloud/configuring-workflow-triggers-776636696.html

I added a link the application navigator to the timesheets so you could access it from anywhere in Jira without having to bounce back to Jira home > Tempo > My Work 

Navigate to the service desk Settings > Customer Permissions Change who they can share tickets with and you limit their access. 

Did you shift it back to Service Desk? Check to see if the system swapped out any of the schemes

https://confluence.atlassian.com/applinks/link-atlassian-applications-to-work-together-785449117.html

Nickle and Dime'd to death is what we call it.

Make note of the screens in the projects you would like the field to appear in. As the Site-Admin G+G > Type Custom into the box > Custom Fields Alt. Top left corner JIRA Home (in the new jira) > Settings > Issues > Custom Fields In the top right of the Custom fields screen 'Add Custom Field' Create the fields and add the…

In Jira Cloud, you can create a "Portal Only Account" that grants the user the ability to use the Service Desk Portal to view issues they have submitted. You can adjust it so that the users can view tickets in this way. 

Clear out your cookies/cache Validate your permissions - might be some additional permissions in place on the project to mask it from user who arent part of Group 'X'

Your gonna need something like Adaptivist ScriptRunner to do this. 

"Issue Updated" should cover all issues which have had their details changed that includes Editing an issue, changing the summary, deleting a comment, attaching files to the issue, linking an issue. On Jira Cloud in the Custom Fields for the Site Admin; if you navigate from the normal list to the 'Advanced Fields' there is…

Once you establish the group, issue type, fields etc. Go into the project permissions and create Issue Security and Permissions. This allows you to mask/hide issues from groups that arent permitted to see the tickets. We do this for our HR department. 

As much as it annoys me from time to time. The Tempo addons do a decent job of this. Their support however is a bit ....ignorant.