Jack Brickey Expert

@Ben Collins , old post...assume this has been resolved. Please update with finding if you recall.

@Gonçalo Santos Garcia , You simply need to ensure customers are not in any project they should not have access to.

Hi @Aaron Watkins , I am not seeing this. Is it possible that these requests are raised by your agents on behalf of customer?

For me, in cloud, the History displays time as well as date.

old post... Maybe the current Automation can allow you to attain your goal?

If you Verify your domain the you can manage the user's details.

Do you have the project configure to automatically add customers? This post does a good job of explaining how Cc emails are handled - How-to-CC-users-into-a-Service-Desk-issue-logged-via-email 

There isn't a means of achieving this.

Hi @Nataly Rios Goico , there really isn't a clear concept of features in Jira. I will share with you some thoughts for you to consider. In the end it comes down to what works best for you and your team. * in standard plan you have epic – story – subtasks so you could use epic as a feature if you wish and then apply the…

So it appears that you have a custom field called "assignees". Note this is plural. I suspect someone may have created a multi-select user field. There is of course the default "Assignee" field that is singular and is what drives those avatars.

Do you literally mean "someone" or do you mean to have two systems monitoring the same inbox? If you had two systems monitoring and marking emails as read then that will clearly create a conflict. If a human opens the inbox and just peruse the mail without marking them as read it would not prevent issues from being…

I wonder if they are using old editor? Roll-back-to-old-editor 

Yes, as below. Also you likely want to check the box "only include issues that have changed since he last time this rule executed." In the branch rule.

Well JSM does support SLAs out of the box JSW does not. However you can certainly achieve your goal using automation and comparing the current time with the due date. It would look something like this trigger - scheduled to run daily condition -JQL status urgent and due date criteria and not resolved action - send email 

here is my example. your implementation will vary. * Rule is triggered when I transition an issue into development status * My first check to see if there's already link issue so that I don't have the case where multiple software issues are created * In my case I want to ensure that this is only run for issue types of bug…

Hi @Frank Le , let me first start by saying that this is a topic often discussed within the community. In each of those cases it is highly recommended not to move JSM issues over to a JSW project. Rather you should leverage the built-in create linked issue. The reason for this is it maintains connection with the customer…

When you enter your email as you first begin to log into Jira you should be presented with a forgotten password link. I recommend you try that.

You might also find this article of interest - Forms-Use-Case-New-Employee-Onboarding-Cross-Project if the new forms capability was in place at the time I was building out my on boarding and off boarding process I absolutely would've used this methodology. I am anxious to give the new forms capability to try as it is quite…

Simply create a custom date field and require that field in the initial termination request rather than having the Requestor include it in the Summary. Invariably having a process that requires the requester to enter a date in the summary in a specific format will fail. Humans are not reliable systems. They will forget to…

Understand, but can the triggering issue not have the date of termination in a 'Effective Date' custom field? We have this very same process. HR will create a ticket for termination and they are required to enter the termination date via the form. Subsequent issues are created and routed to the necessary responsible…

My quick search on JAC didn't turn up any hits.

And you are sure they already licensed Jira SW users? It is insufficient to have site access. They need to be licensed users.

For TMP you don't have option to display the version in the manner you want. You can use the version filter at the top of the backlog but not what you specifically are looking for.

Understood. I'm just wondering if it could be implemented and successfully deployed. Basically, if those opening the tickets are using the portal or the application itself then it is easy to achieve success. However, if your team only creates issues via email then that is more challenging as you end up in the situation…

 maybe this? Set your 14d to... "Time to resolution" <= remaining(336h) AND "Time to resolution" > remaining(168h) and 7d to... "Time to resolution" <= remaining(168h) basically your first one is anything 14 days or less but greater than seven days and the second one is anything seven days or less

That is really really odd. I would recommend reaching out to Atlassian support directly to see if they could login and have a look.

Ah I see

Could you not consider using an Issuetype that has the termination or hirer date as an actual date field? This is typically how you set these on-boarding off-boarding processes up. 

And I assume you have tested with multiple browsers? You definitely don't want to remove her account as I highly doubt that would correct the situation. I assume that she has logged off and log back in? What about other activities within Jira or other projects and boards?

when the Resolution is set. and it will be cleared whenever the Resolution is cleared.