Benjamin_tmh9yg Community Champion

Hi @Wesley Aldridge ...There's a macro built into confluence that you can include that page into your other pages as a main source of truth or a section. Look at the include page or the excerpt macro. This should point you to the right direction. Hope this helps.

Hi @Aqib Shah . Please could you show screens of what you did? Downloads usually end up in your default download directory on your PC.

Hi @Haleigh Welch - Another way to go about it is to use sections. Try a 3 part section and place that macro in the middle. Hope that helps.

Hi @Christopher Searle Since you are the site admin, should be able to course correct this by reviewing the permission schemes making sure the correct roles/groups have browse permissions and admin privileges. Then start fixing the users and roles. 

You got it!

You're welcome!

Hi @Stephanie Willis - I haven't seen a method out of the box. Usually, I see done from a product team is using the status color macros but that's manual input. May want to look into market add-ons like the one mentioned by @Stephan Sutter 

Hi @raj - Just need create the issue collector on the project. Copy the snippet code to your website and it will call out the form to popup. https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/

From my observation, it is design to share with users internally, therefore users are usually already added and the agent searches for whom to share the ticket with. Externally, customers users are not already populated in the system, so the only way to share is with e-mail or agent manually enters them.

@Anna Alabau Difficult to troubleshoot from the cloud platform. May want to raise a ticket with Atlassian support to get support on your instance to look at the issue underneath.

@Carolyn Achtermeier - It is by design. The first one will always show. Here's a tip I use. Go to board settings and put unassigned issues for the swim lane to the top...that way all the users swim lane will be collapsable. Hope this helps.

@Julia Ramsey - Might be easier to create a filter for the department leads and have them subscribe or you can subscribe them to the filter. Those issues will be sent at the interval you have set. You can use the label field to tag the issues for your query lookup. This should take care of what you mention above. Hope this…

You can share the issue by e-mail with the share function on the upper right corner of the page. However, this can't be done from inside Jira. It is design to search for users to select.

HI @Yuval Maron - This post should help you in your direction and explain what can and cannot be exported to word. https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Will-it-be-possible-to-export-test-steps-from-JIRA-to-Word/qaq-p/335021

@Lee Dunsmoor - This is done on the mail client side. When the e-mail is sent out, it is just sent with support@domain.com. Some mail clients will resolve it, using some username but underneath it is support@domain.com. 

Try reindexing your server and see if the issue is gone. If the issue still persist, what is the error that is informing you that this issue is preventing from migrating?

Based on the given information, is your localhost blocking port 80 and just allowing 443 which is HTTPS? May want to check your internal firewall. -Ben

HI @Bill Cronin ...You can do this by using the built in automation. First create a rule where it's trigger by a newly created issue and then set an action to add those 3 people for every issue to the request participants. Hope this helps.

Doesn't need to be. Usually, it use and can be populate with text by configuring the field context.

There should be button in circle on the top right to expand. Hope this helps!

Hi @Natalie Franklin - For receiving request for JSM, the email request is the feature to use. the Jira mail handler is for Jira Software. I believe I ran into similar issue a while back. Tried to duplicate the issue so I can remember the steps but it worked fine. A couple things I would try is make a bogus pop and imap…

 Hi @Rik Fisk ... I don't think you need another system. The design of the application is to collaborate. When multiple teams needs to work on a ticket, there is an option to invite the agents from other team until the problem is solved. or keep them in the service desk project as needed. Same goes when service desk team…

You welcome. There's a tool for inspect permission but it's on the premium plan. https://support.atlassian.com/confluence-cloud/docs/inspect-a-users-permissions/ For the manual way, you will need to check along these steps: 1. Check the space permission. If good, go to 2 2. Check the parent page. If good, go to 3. 3. check…

Hi Adrian, I just tested it. It works. Where is the label placed? Is it on a page in a space? -Ben

Summary is the most important part. Anything that you set as a require field in the issue type tied to the collector page should be shown. Usually, when using an issue collector, the best practice is keep it simple possible since the user could any type of user. Therefore, as admins, we want to make it easy to use so they…

You welcome. That would depend on your storage size. usually, the items really that take up the most space is the attachments and not the ticket itself. 

Great! Somewhat. Essentially, a queue is a JQL filter. For example, if you have jql filter based on an organization, all those tickets will go to this queue. Then inform that team to focus on that queue. Queues are a great way to help team focus on a list of items. You can use it to focus on customers, high priority…

Hi @scof ....The permission scheme or access might be impacted. If you have jira admin permission, you can check on it to make sure the agents are still included in the project and the scheme is correct. -Ben

Hi Bob...there isn't a way on cloud unless you are on server or DC in which you have access to the database to manipulate the configuration. Same is mention in the documentation: https://support.atlassian.com/jira-cloud-administration/docs/edit-or-delete-a-custom-field/ Here's a way you can go about it: Create a custom…

Hi Jane, In order to archive, your user must have the Jira admin or Jira System Admin permission. Make sure your user still has this permission, this is configured by the Jira admin. Hope this helps -Ben