Jack Brickey Expert

Another option to consider is to use automation to create a new task altogether when an issue is moved to Done w/ a specific resolution that indicates it is ready to be tested. You can use smartvalues to pull in the triggering issue's summary, etc. and link the two. Personally, I prefer separate issues as it retains some…

yes it should since scrum boards base the metrics off the right-hand most column. I would likely consider a more complex "resolution" implementation, e.g. when moved to Done set the Resolution to say "Dev-complete" and then when moved to Closed to maybe "resolved, complete, done, etc.". yes the boards overlap w/ Done, e.g.…

Hi Doug, No i'm not advocating any solution specifically for pair programming with TDD. I did not read that into Samantha's post. Admittedly, that underlying detail might apply here but it is just as likely that it does not. What I was attempting to convey was: * this is my opinion * the Jira solution focuses on single…

well it depends on your workflow TBH. If "Done" status ultimately goes to subsequent statuses, e.g. UAT which then can say move to "Closed" then you can certainly do this and I have done something similar before (see below). Now if Done is in fact the final terminal state then this wouldn't make sense as you couldn't…

No and you should not IMO. What you should consider is to have a parent task and create sub-tasks under this parent assigning them to the individuals. This will ensure ownership and accountability will be maintained.

yep, ghosts in the room for sure.

i'm not going near that place. a big nope.

LOL...that would certainly cause one to jump out of their seats. That was one of my favorite scary movies for sure!

You would need some scripting or automation addon. I have use Automation for Jira successfully for this scenario but there are certainly other addon solutions.

Hi Noa, so Atlassian is replacing the original “Automation” and renaming the “Project automation” to “Automation”. Now what should be happening is that all of your older “Automations” will have been converted to the new automation rules. Did you look under project settings > automations? You might see two sub-screens -…

Reasonable question. I can’t say TBH. My bet is they will be lost. Worth a test for sure.

:-( as i feared. some random thoughts.... * Contact support to see if they can/will bust it free. If it can be done they are the only ones that can for Cloud. * I would like to understand if a process of first renaming a field to something else before deleting would work. That is, let the renamed field get locked so you…

shouldn't need SR. try to create a JQL something like this.... project = abc and issuetype != bug or (issuetype = bug and "my custom field" != Xyz)

Interesting question Liam. I have never attempted but you can certainly delete SLAs. Project settings > SLA and click on the ellipses (see below). Now the question becomes will you be able to reuse the "manager alert" field. I think so but you will need to test it out. As you are likely aware some 'delete' or 'rename'…

Disclaimer - I have not played w/ Issue Security. With that said, why couldn't you have a unique request type that also has a unique issuetype and define the necessary issue security for that request type? In this way if I need to create a 'private' request I simply select 'Private Request' on the portal.

You might check out this site - https://www.atlassian.com/partners 

this is not something the Customer can do. They can "not share" the issue which would ensure that other customers in their Organization would not see it.

I don't see an approval here, or certainly not obvious. Everything is an "all" transition which is counter to the Approval method in JSD. I was going to add a reference to the Atlassian docs on Approvals but just went to locate and the search function is non-functional. :-(

In that case please see Kristian's answer as it is the correct answer.

You can’t export dashboard data directly other than screenshots, so yes, you would need to export the results of the filters to CSV/excel.

That is really messed up for sure. Definitely contact support and have them log in and take a look.

Hi Niels, here is what I see in my instance. Basically, both automations are now listed under “Automation page” accessible in the same sidebar location as the original JSD location. the old JSD Automation is renamed on that page as Legacy automation. And according to the banners there you will not need to do anything as…

This is one post that speaks to the issue of using a classic Kanban board with a mix of classic and NG issues. 

Agree with others on reassigning and I would even consider leveraging automation to reassign at departure and the assign back to the original agent upon return. Of course there are exceptions to consider so what is best depends on your situation and customer relationship as Nic indicates. 

This isn’t supported today. There is a suggestion to add this capability. You might search the community for other similar posts if interested.

Hi Rob, that is correct. You might check out various addons in the marketplace but I’m not personally familiar with any. Maybe EasyBI? Or consider connecting to MS PowerBI or simply leverage export and Excel. There is a free extension for Excel tha would allow you to query directly from Excel and then build your own charts.

I think the filter you want is as follows... sprint in opensprints() and assignee = "user A" or assignee was "user A" it is hard to decipher your image give everything is obfuscated. :-) However, keep in mind that with the above filter you will get issues on the board that are assigned to User B. I don't know what you mean…

A bit of a different spin on the same thought process.. reminders are like SPAM. Just more emails the team will ignore. Try pivoting the team’s behavior toward using “Your work” or personal boards or dashboards on a daily basis. Put the accountability in their hands to stay on top of their deliverables. Also, this is where…

I don't know what "address" field is. I suspect it is a custom field. You should click on the "configure" link at the bottom of the righthand sidebar (in your image) and ensure the field is part of your screen.

the only other solution is to get the admin of the other project(s) to add you to Manage Sprints. However, keep in mind that this could be dangerous since you could pull in issue from project B into your project A sprint and move them thru the process which would have adverse effects on Project B's sprints potentially.