Stephen.Lugton Community Champion

@Kacper P You can do this without needing a plugin: First create new date (and time if you want) fields for each status you want to track. Then create an automation that triggers on status change, and use a branching if/else structure to set the appropriate custom field to now() You can then add these fields as columns in…

@David McMahon if you don't mind adding a label like that then you could set up automation along the lines of: But note that this will only add labels for start date changes after you implement the automation

@David McMahon with standard JQL this is not possible, unless nothing else has changed since Start Date was updated, in which case you could use 'updated' to search against, but this can't be relied on. This is because JQL looks at the current state of any field and not previous states or when a field changed state,…

@Dennis Rünzler you could get a new role created e.g. "Read only" or "Commenter" (a Jira admin will need to do this), then from your JSM project settings>People assign that role to the required people, and under JSM project settings>Permissions assign that role to "Browse Project", "Resolve Issues", and "Add Comments"

Great idea, I'm going to be renaming my automation for this!

"It's a trap!" for when someone tries to assign a ticket to a project/delivery manager

A couple of questions though: * Why are you cloning a ticket both when created and when updated? This will keep raising a cloned ticket every time a change is made to the original ticket. * Have you considered the option of creating a board in their project with a filter something like: Project = "Your JSM" and "Request…

@Leon Gumba The way that automation works is that the automation only runs if there is an action to trigger it, unfortunately for what you are trying the first automation is not providing a trigger for the second one. There are a few things you could do: (1) In the the rule details of the first automation check the…

It was the comment about the Lego model that reminded me of this; the Lego retrospective. I had managed to get the whole team to come into the office on the same day, and I wanted to do something fun rather than the usual video call retro. So I filled up my backpack with as much of my daughter's Lego bricks as I could…

When my daughter was 2 or 3 we took her with my parents to an ice cream parlour in the local high street, that's not where the shopping story happened, but afterwards we walked back through the shopping centre. Being somewhere new and fun, my daughter was really excited so we had to go into every shop as we went past,…

@Stacey Telford This appears to work to update tickets that don't already have the epic summary: It's a manual trigger so make sure you have the right branch JQL and edit values then run from any ticket in the project that doesn't ned to be updated.

Board B will have a filter like this, even if you move it to another project the filter will stay the same and show the same tickets, as you can see from the images below my board pulls tickets from the TCS project but it's located in the TIS project. Unfortunately permissions access is at project level not board level so…

@Vishal Gogari A simple way to do this would be to create a new project and move Board B to that project (it would still pick up the same information as before since boards are based on filters), and then use project level permissions to restrict access to the new project to only people added to the project. You would have…

You could also use that type of filter to create a new board (with the columns set up to be the same as on their other projects / boards) and changes to tickets on that board would reflect back to the existing projects / boards. It doesn't even matter which project you create the board on as long as they have project…

@Amitava Chattopadhyay you just need to create a filter for that team e.g.: "Team[Team]" = 9ab1685a-2484-43f1-bb61-0fcb9c3adc09-62 or even "Team[Team]" = 62 along with whatever other filtering you want e.g.: "Team[Team]" = 62 AND statusCategory != Done You can then save that filter, and either just give them the filter or…

Taking more of a Star Trek than a Star Wars approach, we make sure to include the Prime Directive: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."…

Unfortunately that is not possible out of the box as the validation that allows automation only takes effect when the ticket is actually created. However, it may be possible to do this using an app plugin but I don't know if any apps do this as again they may run into the validation only occurring on creation issue.

@thiago there is no default field type that would let you do that. It is possible that an app exists but you would have to look at the app marketplace to see if you could find one.. You could also add a validator to a workflow transition to check that the format of the serial number is correct and if not stop the…

@Yousuf Al Rawahi you can do this with automation: When assignee changes Then change other field to be their manager (you will have to use if to choose which manager to assign, and update the automation when users leave or join) This will not update the manager name on the create view but will take effect after the ticket…

@Deepti Agarwal is it possible to get your workflow updated to add in a SIT or UAT status? (but have it also able to go straight from review to completed) If not you could: * Use a label to identify SIT tickets and show labels on the tickets on the board labels = SIT * Flag tickets that are in SIT/UAT so they appear in a…

@Cherelle_Annon The status In Progress allows all statuses to transition to it as shown by the All next to it, that is where the 'transition to' comes from. Edit the status and uncheck the check box next to 'Allow all statuses to transition to this one' The same is true for the other statuses that say 'Transition to'

@Julian Gonser , the automation below creates a task on a weekly schedule, and then creates 4 subtasks with that task as a parent (I've only shown 1, but the other 3 are the same just with different summaries and descriptions

All I can think of is the cafeteria scene at the end of Shazam where Superman walks in carrying a lunch tray.

@Jorma Polvi It looks like you're using a team-managed project, and you're limited to what issue types you can add on a team-managed project. If you need different types of sub-tasks you would need to create a new company-managed board, migrate your existing tickets to that board and then get an admin to create the subtask…

@Rohan Swami That's a good start, looking forward to seeing how the implementation works for us

+1 for this idea

@Neha Tandekar A couple of things to check, unfortunately we don't really have enough information available on your setup to solve this without more info * Do the tickets meet the filter for the board? * Are the board columns set up to show the statuses that those tickets are in?

@Stacey Switzer there's an option in Project settings under Customer Permissions to set who can submit requests: and from the ticket on the portal you can share the ticket with specific users

Hi @Andy Rosengard I use Automation to add a form and then send a comment to the customer, in the example below a form is added after approval for internal customers to fill in a form when they complete the work: Just update the transition that activates the automation and modify the other aspects to your needs.

@Vera Valshonok From the left side bar choose Project settings. Then choose Workflows from the left sidebar. Find the Workflow that you want to assign the Email Request to, and choose (assign) from the bottom of the list of issues assigned to that workflow. Then finally choose Email Request from the list of ticket types,…