Esther Strom Community Champion

@Matt Tse - is there a cutoff date for when the option to turn on/off will be available? Or will users always have the option going forward of which navigation to use?

Are there any plans for a Google Cloud Build integration with Jira Cloud? We have some teams on Bitbucket/Pipelines, others on Circle CI, and a newly-onboarded group who are using Cloud Build. It would be really nice if all teams could access their build info for dashboards, regardless of which tool they're using.

Most of those issues should not have been marked as breached. For example: This issue has a priority of Low and was created 12/22/2019. Based on the SLA goal for Low priority, it should breach at 168 hours. It did; when I mouse over the SLA column, it shows the actual time spent as 264 hours, which does account for the -96…

I think I must be doing something wrong; editing the SLA to include the date does not update the tickets that have already been marked as having breached. Here's what my SLA looks like; note that I've tried both created and createdDate with the same result: And here's what my queue looks like. Based on created >…

Oh, that's a good idea. Don't know why I didn't think of that. I'll give it a shot, thanks!

Our filter is super-simple: project = RALTSS AND component = "Team PegaSUS" ORDER BY Rank DESC Here's the strange thing: we've made no changes at all to the filter or the board settings since I posted this Friday, but when I look at the backlog now, I'm no longer seeing the issues in question. Maybe it just took time for…

Sorry, I just noticed the second screenshot doesn't make it clear that you're seeing the final column. Yes, the column labeled "Done - Truly Complete" which contains the Done status is the final column on the board. That's why we're confused as to why these issues are still displaying.

Thanks, Nic. I had a feeling it would turn out to be not currently possible, but I hoped.

Thank you for your response, @Petter Gonçalves We've never used the "simplified workflows" that are "managed by Jira" before. My understanding is that if I edit one of those workflows (outside of the board), it will become a managed workflow. Is this not correct? That is unacceptable at this point for this project.

That sounds like it makes sense, but I don't think it's the case, as we have epics in other boards using the same color scheme that don't use the bold text for low contrast: Also, the black on gray is the highest contrast, so it makes no sense that it would be the one that uses bold text above. If anything, I'd think it…

We are on Cloud; it doesn't support scripted fields.

Thanks, Mohammed. Unfortunately that doesn't help with our existing tickets, which is what we need to get this data for. I think I'm going to have to export the info to Excel and figure things out there, which I hate having to do, but oh well.

Thank you, but I know that query will not get us what we need, because updated will get you any ticket where any of many fields were updated. We need to be able to specify specifically when the labels field was updated.

Thanks, Nic. That's what I figured, but thought I would ask - Cloud changes pretty frequently, and it's not impossible that I might have missed a notification about new logs becoming available. 

I did already look there, but I don't see anything that would explain the error. I thought there might be another log somewhere I didn't know about.

Like I said, it's not perfect :) But it's more than we had before. As to distinct issue keys, I don't know - you'd need to contact Atlassian about that. You could comment on the ticket that announced the new functionality, but I don't know if Atlassian pays attention to comments on closed tickets, as they have not…

@Manikandan Muruganandam - I had the same question, and contacted Atlassian support. This is their response. "You are right, because of the SAML SSO integration, reseting the users' password won't have any affect in the way they log in. However, even if they don't use the Atlassian password to log in, the reset password…

ETA: never mind; I found it. Click the cog icon in the actual team. Thanks. Thanks, Mike. I'm fine with ignoring them, but it's confusing to our users. Neither Samantha nor Jeff is a team lead. Where would I find the "approve timesheet" permission? When I click on the Team permissions section, the "click here" just takes…

As an update to my recent comment (and a possible answer, however late), I want to point out that Atlassian has very recently introduced a new JQL function called issueLinkType, which can be used in filters, but also in boards. It's not perfect; if you're already using card colors for something else, you won't be able to…

The documentation is a bit fuzzy, but setting the Summary field value (at the top, in the "set fields of new issue" section) to {{it}} gave me the results I needed. 

Thank you! That did it.

Thank you! That's what I needed.

I know this is old, but since it appears that it's still one of Google's top search results, I wanted to add a clarification. There have been a few comments from users saying they're administrators, so of course they have access to create issues. This is not something to be assumed. It's entirely possible, and there are…

Thank you. That's a server ticket, as indicated we're using Cloud. I was able to find the corresponding Cloud ticket, which has been open since 2008 and very clearly states by Atlassian that it will not be implemented. If what you say is true and the functionality is being developed for Cloud, could you please have someone…

Just curious how this would look now that we're using the new view on Cloud - we no longer have individual buttons for transitions; just a single dropdown.

Thank you, jira.permission.work.denied does work. I hadn't seen that one mentioned in any of the search results I found.

@Marc Mercer I agree with you for the most part. I do think that if they're determined to have a new UI, it should just be applied across the board, as it's confusing to our users as to why they have two different interfaces depending on what kind of content they're working with, and whether it's new or old. Just FYI,…

Thanks; I was not aware. We haven't received the new editor rollout for most of the page types yet. 

FYI, there's an open bug that indicates that validators are ignored when customer transitions are performed. So your solution may not work.

Just to clarify, that only works if everything but the destination of the transition is identical. If Approve from A to B has different conditions, validators, post functions, etc. than Approve from A to C would (which is fairly common), then you can't re-use the transition, and you can't have two separate Approve…