Jack Brickey Expert

Ha…yes indeed

Exactly what Alex says - know your audience. I also just realize that there’s questions being asked in the JSM collection. If indeed you planned a GSM project for your finance team then this article might be more appropriate. what-are-the-project-templates 

I wonder if we are dealing with a TMP-Automation limitation here. I see that Oliver is using TMP. I haven’t attempted in TMP myself.

I don’t know of a recent document on this TBH. I found this article that may be of some use - use-jira-work-management-for-task-management . On that page you will see other articles explaining other use cases. These should roughly align with templates. The thing to consider is what is the workflow for the Finance team.

Of course you could simply create a queue for issues >1000h

Unless something has changed you need to have JSW or JWM to have the dashboard feature. You should have a Dashboard menu item on the Jira menu at the top of your screen. Assuming it is there click it and select Create dashboard. If you need assistance with creating a dashboard beyond that let me know.

Below is a detailed issue view where you can click on the ellipses and select convert to issue

correct. One way to see the issue type into change in select issue type is by clicking on the issue type icon as shown below in the image.

Check the underlying filter that forms your scrum board - Board settings > general, view and edit the filter.

I assume you have considered creating issues by email? Where you can share an email address with non-Jira users that they can use to submit requests.

* Administrators and agents are licensed JSM users * Customers do not require a paid license * Collaborators is just a term often used to refer to licensed Jira software or Jira Work Management users that are licensed and have browse access to a JSM projects. These users will not need to have a JSM license as they are not…

I’m not exactly sure what that means. You can edit an existing rule which will in effect override the old rule. You could delete or remove the old rule and create a new one.

I strongly recommend against deleting issues. Once they are closed they should be nice and quiet and should not require any maintenance and you will have them there in the future should you need to go back and review.

Hi Karen, unfortunately this is a public forum and we have no access to your specific data as it should be. In any event if you believe that your admin left the company you could reach out to Atlassian support and select billing option and see if they can assist. However you should attempt to find out who administers your…

Billing is not at a project level it is on the application. So if an agent is on 1 or 10 JSM projects that is a single license. regarding groups - groups consist of licensed users. Once a person is licensed they can be in as many groups and projects as you like without additional charges.

I suspect it has been deleted.

Trying to keep the convo within a single thread so use the reply button rather than Answer… not sure how the first option results in a non-clean portal. You might read about approvals here - set-up-approvals I don’t follow the question of “accessing” customer from another project. You cannot but not sure why you need to.

Based on the limited details I would offer this - google-sheets-integration 

Sure. The company B admin needs to add you as an admin on their site.

Is it possible that someone deleted the sprint?

It doesn’t seem that the sprint is active if all issues are back in the backlog. If you look at one of the issues that was in the sprint what do you find in the Sprint field? If the sprint exists it should show in the Sprint Report for bot active and historic.

Can you verify if the customer request type is set and is the customer the Reporter?

Have you looked at the email logs? Go to project settings, email requests then click on the view logs for your email handler. It may be that the from email is not a customer.

JSW and JSM are separate applications. If you have a user that needs both then you will pay for each license. If the user only uses one then they pay only for that one app. The one exception is if a licensed user of JSW has only browse access (non-agent) in. JSM project there is no additional charge.

One idea - allow all customers to see and make those requests but set up approval on those requests such that the admin customers would need to approve before the agent worked the request. The other option is to use different projects, one for all customers and one for admins. Finally, you can also investigate Issue…

I use the connector for Cloud without issue. Have you contacted vendor support?

Can you first try to simplify your goals? It appears that you want 9h for any issue in this project so remove the two Issuetype entries. If this does not work then delete the SLA and recreate.

Hi Greg, welcome to the community! I am not quite following your use case but let’s dive in an figure it out. With JSM there are two types of users and the possibility of three. * agents - those users that can be assigned and work issues to closure in the project * customers - those users that create issues to be worked.…

Nice article @Teodora V _Warsaw Dynamics_ . Thank you for sharing as I’m always interested in seeing how non-dev teams leverage Jira and Confluence. If we both make it to Summit in 2022 would love to hear more.

This this is a custom workflow so you would need to ask the author of the workflow with the intentions are between those two statuses. Just looking at it my guess would be they intended to allow one party to move it to completed and then another party to say when it was actually considered closed. A good example of this…