Jack Brickey Expert

Let me rewind here a bit. Who created the issue in the project initially and how did they do that? From what I read initially it seems that the IT agent created the ticket for the customer. Then the question is did they use the create button at the top or did they use the raise a request link on the side bar? If they use…

Did that solve your issue? Or is the problem persisting?

Please verify that the customer request type is actually set. There are two things that need to be set correctly when raising the request on behalf of a customer: the reporter and the customer request type

You could use automation for this. Here is an post where I previously offered the solution -how-to-automatically-close-an-epic-based-on-linked-issue-status 

Ah. Maybe having the dots in the serial number is causing the issue. What if you test in the serial number field number without dots. Can you search and find the issue in that case.

I am not even familiar with waiting on support time to be honest. Could you share a screenshot of where you are seeing this?

I don’t understand the statement “external email addresses are not “. Please explain your issue further so I might be able to assist

@Marlene Kegel - codefortynine , cool. You might want to update the Marketplace details. Cheers!

First I will point you to the documentation - automate-your-jira-cloud-processes-and-workflows the concept of automation flow: * trigger - the event that results in the rule running * condition(s) - if there are conditions under which you want to execute the action then include * action(s) - the actions that should be done…

You could link the issues and use Automation to update the JSM ticket based upon the JSW issue updates. There are a lot of posts in the community about how this is done.

First is important to understand that for anyone to open an issue in a JSM Project they must be or become a Customer. So all of your internal employees will ultimately have to be listed as a customer in your internal projects. Second regarding the portal and what customer see - A customer will only see the project where…

Did you happen to start with a paid version? Go into the administration area and billing > manage subscriptions. Check to see what plan you were on. It will either say standard or free. If standard then attempt to change it to free.

Do issues show up when he clicks on the filter. If so are there any quick filters that could be interfering with what the user is saying or not seeing on the board?

That would certainly be odd. Tell me more about these projects. Is it possible that these are archived or trashed projects?

The extension is free. I won’t attempt to answer the question on whether it’s safe or not. I think that is a subjective decision.

@Shahbaz Khan , if you inspect the subtest that are seemingly holding the sprint closure up what status are they in? I might suggest clearing the sprint from the Sprint field on all issues if in fact the stories and subtasks are clearly no longer in the sprint.

That is a very old issue that was fixed in 2013. If that is the cause of the issue here that it needs to be reported to Atlassian. However I wouldn’t suspect that just yet.

Consider using this free solution- jira-cloud-for-google-sheets-official set up your JQL filter in Sheets and schedule to run monthly.

Is the error message indicates your question needs to go to your admin. The community here doesn’t have the ability to grant that permission. Note the option is either on or off there isn’t a trial basis. If you aren’t going to be creating projects often I would definitely have your admin deal with this as there could be…

Something to try… with each JSM project Atlassian gives you a dedicated email. You also have the option to add a custom email. Try to configure both. I just verified in a test project that I could create issues sending to both addresses concurrently. now you have to figure out how you want to separate these out in your…

Yep.

just retracing our steps here… please verify that BOTH the filter used to create the board and the board itself are shared. Check to see if one of the users can find and access the filter. If they can find the filter and issues are displayed then that is a good thing.

By “letters” I assume you mean emails? Regarding the Cc list are these individuals Customers of the project? If so they should be added as Request Participants. Is that occurring?

You may wish to vote/watch this suggestion- JRACLOUD-7990 

* You will need to perform multiple moves or consider a marketplace app, e.g. deep clone which allows for 5000 currently. * you will need to educate folks to use new email or consider using an external forward though this can be problematic if you wish to retain the original sender. * this will be a manual process.…

Ah I see. That is certainly important info. Unfortunately it is not possible control the ability to create a sub task based on the parent’s status. I doubt either of these are useful but… You could limit who can create the sub task via condition on the create. You could use automation to close the created sub task if the…

If you remove the sub-task Issuetype from the project then it should disappear. I have not tried this but know it is not there in my projects without subtasks. Also if you already have sub tasks in that project you would need to move to tasks/stories.

Cloning does not result in comments being mirrored. You will need to use Automation for this. I would also recommend using “create linked issue” rather than clone.

Do you mean to say that you commented on the issue in Jira software and you cannot see that comment in Jira service management? If so that would be expected as the issues are separate. If you want to hav3 the comments mirrored you could use Automation.

Creating another board in a project does not create another project. This new board you create could be the go to board for your team. Yes there will be the remnants of the old board there but that is simply a training issue. Regardless even if a user goes to the old board it’s not going to mess anything up. In fact if a…