Mikael Sandberg Community Champion

What ticket number are you looking at to generate? When you create a request it will automatically be assigned a key, which is the project key and a number. For example JSM-1, JSM-2 etc.

You could do this by using a combination of git sparse checkout and shallow clone. Have a look at this thread on how to combine these commands, https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/28039894#28039894

Hi @Rutuja Jadhav, Welcome to Atlassian Community! Do you know if the page you are editing is using either the excerpt include or include page macro? Based on your description that sounds like what is happening here. 

Hi @Sherri, Welcome to Atlassian Community! You can set up Trello to use SSO, but you need to be on the Enterprise plan and have it linked to your Atlassian organization via Atlassian Access. See Linking a Trello Enterprise to an Atlassian organization for more information.

Correct, if all your employees have to be available to be added as watchers they would need either a Jira license or JSM license. If you want your watchers to be able to reply to the customer they have to have a JSM license, if they should only be able to add internal comments they need a Jira license. I would recommend…

Yes, users that you want to add as watchers have to have either a Jira license, you can then add them as users in the project and they will be able to see the requests and add internal comments, or has to be an agent (JSM license). Request participants do not require that the user has a license, they just have to be added…

Hi @Deviprasad Marotu, Welcome to Atlassian Community! You can only add users that have access to the JSM project as watchers. If the user you are trying to add as a watcher only have access to the project as a customer you can instead add them to the Request participants field. 

You can always sign up for a free instance, it allows you to have up to 10 users on it. Have a look at https://www.atlassian.com/software/jira/pricing

You may want to contact Atlassian support, sometimes emails that bounces once ends up on their suppression list. 

No, automation does not have an action that allows you to add an attachment, it only have one that allows you to delete attachments.

The legacy automation does not allow you to specify the user, so you should consider recreating this automation in the new one instead, then you can add a condition to ignore changing the status if the user is Automation for Jira

Hi @Mohan Rao, Welcome to Atlassian Community! If you create your changes by using the Create button in Jira that is possible, but not if you create your changes from the portal. When you create an issue using the Create button it uses a screen that you have assigned to the create action and you can then add a message…

If you click on Legacy automation, do you see these two rules? The "Comment updates reply status" is the one that changes the status when a reply is added to the request, including replies from automations. You can modify this automation to only have it run when the reply is done by an agent for example

Hi @Paul Sandmair, Welcome to Atlassian Community! Yes, you can do this. One way of doing it is to add a new status in your workflow and a custom field for the user that should accept the story. On the transition out from the new status you can add a condition that only allows the user in the custom field to perform the…

Hi @Kim Nielsen, Welcome to Atlassian Community! You cannot change the left side bar out out of the box, you would need an app that allows you to redesign the space, like Refined for Confluence or Linchpin Intranet Suite.

No currently you cannot send DMs, but that is on our community wishlist. For now Linkedin would be the best bet, just click my profile and go to Social.

Hi @Douglas Souza, Welcome to Atlassian Community! You should be able to to change the automation that moves the request to Waiting for Customer so that it would not do that if the user is not an agent. You can find that automation under Legacy automation. 

You should be able to do that if you use the IQL branch statement as a select and then update the object. Your other option is to use the REST API and do a send web request to Insight and update the object that way.

Boards will follow the same permissions as for your project, you cannot set it up so just a subset of users can see the board. As long as a user can browse the project they will be able to see all the boards associated with the project. 

Have a look at Basic auth for REST APIs. Instead of username:password you should now use username:token when using basic authentication. You can Base64 this if you like. 

Yes, each board has its own filter, and as a board admin or project admin you can change that. Have a look at Configure filters for more information. No, you cannot limit the issues available based on the board, if you want to do that you would have to have different projects for the teams.

Hi @Jeff A, Welcome to Atlassian Community! Yes, this can be achieved. All you have to do is change the filter used by each board to only include the issue types that each team is using. 

You cannot archive individual issues, but what you could do is have an Archived status and then change the filter that you board is using to exclude issues in that status.

It depends on what you are looking for, I could give some advice on it since we are using JSM for HR. But if you want someone to come in and help you your best bet is to contact one of Atlassian's partners and they can help you.

If all that is configured correctly people in cc should be added as request participants. I would verify it by testing to add people to a test email and make sure that they are listed as customers.

You cannot embed the built-in excerpt macro in a table, instead you would have to use an app for it, Table Filter and Charts for Confluence, which looks like it can do what you are looking for. 

Hi @Meaghan, Welcome to Atlassian Community! Yes, you can do this using the excerpt macro on each project page and then on the overview page you use the excerpt include macro to display the information.

You could use the JQL condition to check if the custom fields are set to a specific value instead of using the field value condition. I haven't seen this issue with custom fields, but I have seen it with new request types not listed and used the JQL one to work around it.

Currently that is not possible, but once automations is added to Confluence you might be able to do that. The last I heard was that automation should be available by end of the year, but that might change.

Edit restrictions are not inherited down to child pages, but view restrictions are, so when you do the inspect restrictions make sure you select view to see if any parent pages have that restriction.