Jack Brickey Expert

Hi JJ, I was testing this in my cloud instances and in fact the request type is carried over. I assume the original issue has a request type? One more question, is the issue type the same for both?

Unfortunately access to Reports is not independently configurable. At least this is the case in Cloud but I expect the same applies to self-hosted.

First I would verify that the customer is using the view requests correctly. They need to select all requests by any customer. Next, verify that the Customer Request Type is set vs. no match. Can you confirm the reporter can see the request? Can you confirm the customer,er shared with show under Request Participants?

So do you mean you have the sprint name and you want the ID? if you go to the Sprint Review report and select the sprint you are interested in the drop down then the ID will be at the end of the url.

Owl, it depends on how you define access to JSD. Let me try to explain. * Agents are those "licensed" users that can access the application, take ownership of issues and manage all aspects of the issues. * Admins are licensed users that have full access to the application as well as all underlying configuration. Note there…

Yes it is rather non-obvious. glad it worked for you.

Hi @COO , we need more info here. Excluded organization? What does that mean? How are you excluding? Are you saying that you removed an organization from a project and later it reappeared or something else?

Mark, I’m not where I can test something out myself but this should be possible. Here is a similar post you might look at - Auto-Transition-of-issues-when-the-linked-issue-status-changes I am assuming your requirements are something like this: * let’s say you have issue A and issue B... * you want A to move to Postponed…

Hi Chantelle, that is an odd error. Have you tried other projects? Can you create tasks ok, just not sub-tasks? Do others have this same issue? Depending on these answers I suspect you may need to reach out to Atlassian Support as it may be something weird with your instance.

Check that you do not have a default value for your resolution field. Jira settings > Issues > Resolutions at the top you will have a link to "Clear defaults"

Hi Oliver, can you go to Project settings > customer notifications and inspect each of the notifications via “edit”. Note I just saw the last part of your inquiry. You will not be able to modify the default links. You might consider an addon like JETI, replacing the JSD mail handler altogether. 

I would thoroughly inspect the Customers screen. It may be you have the person in an organization that is in both project. It also may be that one of your projects is public. Please share some screen shots of your config,

For the last part of your question you could use card colors to show issues that are past Due date. Use a JQL like - Resolution is empty and duedate <= startOfDay(). Note this assumes you are setting Resolution when issues are moved to Done. The first part is a bit more tricky and you really cannot achieve OOTB. At least…

Hi @JConstantine , it is not possible to configure notifications by Issuetype unfortunately. There was a similar post recently and you might find a suggested work around useful - exclude-sub-task-creation-notification 

Hi @Soporte LeanPMS , I would suggest the following reference - permissions-overview . I suspect that your users are going into a default group, e.g. developers or jira-users and the permissions for your projects are giving access based upon that group. start by going to project > Project settings > Permissions and inspect…

Hi @Johnathan Garrett-Sinclair , it seems the goal is to ensure the right folks have access to the board. You wouldn’t use the sub-filter for this. Rather, you would share the board by group or similar. To do so, go to Board settings (ellipses in upper right) and select General and click Edit filter shares (see image…

love the accept answer solution. will be interesting to see if that changes the acceptance numbers

Hi @Mike Bowen , so you are using the old issue view still so the way you remove fields from the "detailed issue view" sidebar on the board is to go to Board settings (ellipses in top right) and select Detailed Issue view. Find the fields you wish to remove and delete them.

I’m not exactly sure what you are wanting here but wonder if the cascading field would meet your needs?

You mention the ticket is shared with another “organization” do you mean that or do you mean another customer within an organization? Which option is selected on your Customer Permission config?

Hi Manish, I just checked and the history is shown which is what I expected. Below is the new issue view of one example. I click on the “+5” in my case and it expands to show the other sprints.

without understanding more on your specific case I would suggest the following steps: * Assess if there is anything unique about the customer as compared to those that work * run a clean test - have the customer send in a new request and see if the receive a create notification. Do this on the phone with them if possible.…

No you can simply create a new board.

Something like this maybe? createdDate >= startOfWeek() and resolution is empty you can set up a subscription and run it at the end of the week. Note this assumes your are setting the resolution when moving issues to Done.

Your best bet is to simply create the project from scratch. Then create issue types, custom fields, workflows, add the agents and customers. Yi7 night wish to read this guide - get-started-with-jira-service-desk 

This is done at id.atlassian.com and only by the specific user.

I don’t understand your question here. It seems more like a statement of facts describing a recent week’s activities. 

There isn’t a role/permission for read-only customers.

If the user is a customer they will be able to create issues. There is not a read only customer role/permission scheme.

My $0.02 is to allow users free control. Yes you may have to live with a lot of stale labels but in fact the Labels field is intended to allow users a free form way of tagging issues.