Walter Buggenhout Community Champion

You did the right thing by raising a support ticket, @Sourav Yadav. You need Atlassian support to look into this - most people here in Community - like myself - are volunteering to help users by sharing knowledge and answering questions, but we don't have access to the Atlassian systems. 

Hi @JOY, no worries. That's a matter of playing around with your criteria and parentheses: project = TIME AND issueType in (Story, Subtask) AND ((sprint in closedSprints() and status = Done) OR ((Sprint in (futureSprints(), openSprints()) OR sprint = EMPTY) AND Status not in (Done, "Won't Fix")))

Hi @Berat Altunhan, Have a look at the separation of duties condition to implement this. It implies that a user who performed a previous transition between 2 statuses should not be allowed to execute the next transition, which looks very much what you explain here. Hope this helps! 

Hi @Janluca MARIS and welcome to the Community! There's several reasons why issues may not be visible on your board: * Your board is based on a board filter that you can manage in Board Settings > General. Any issues that are not returned by the filter will not be visible on your board. * Your issues go through a workflow…

Hi @JOY, If you want to exclude done items, you'll need to make that explicit in your filter statement. Have you tried something like this? project = TIME AND issueType in (Story, Subtask) AND (Sprint in (futureSprints(), openSprints())OR sprint = EMPTY) AND Status not in (Done, "Won't Fix") Hope this helps!

Hi @Gary McDermott, Which issues are visible on a board is determined by the board filter (configurable via Board Settings > General in company managed projects). From what you describe, it seems as if you have boards set up for individual users, as you seem to be retrieving issues by the assignee field. It is more common…

Good call out, @Bill Sheboy! No, it is not. But it seems to come with Jira Service Management. Since I have the entire Jira suite of products on my test instance, I did not think about the origin of the gadget. 

Hi @Eden Peretz, Instead of associating the screen with a screen scheme, you should associate it with the transition to the Done (or Closed or whatever your final status may be) in your workflow. To do so, edit your workflow, select that transition and click the Edit button in the dialog that appears: You can associate…

Maybe worth mentioning that I noticed a slight delay before the assignment to the previous assignee was displayed. This is - I reckon - because the automation rule runs asynchronously and kicks in after the issue is updated to the previous status.

I have just tried this myself with the following setup: Just worked as expected. I did make sure to verify that the issue I tested with was indeed assigned and assigned to someone else before making the transition to the review status in my example.

Hi @Yaroslava Savchuk and welcome to the Community! I am a bit confused by the last sentence of your question, where you say: Earlier I used this app on other projects and everything was okay. If you used the app already in your current Jira site, then you should not install it again to use it for other projects. It should…

Hi @Dan Friedman and welcome to the Community! Your question seems to suggest that not all releases you expect are there. Having checked the documentation and playing around a bit, I see every single release I create appear on the roadmap view. Maybe a couple of things to check: * since releases are mapped to the timeline,…

Hi @Surya Sam and welcome to the Community! From your description I assume you would like to build a table that displays the trend of those different metrics over time (or in your case, across consecutive sprints). Jira does not support that type of advanced reporting out of the box. If you would only like to report on the…

Maybe a bit late to the party, but never too late to catch up with awesome content. I particularly like the approach that really digs into an inspiring story, gets a lot of expertise around the table and combines both fun facts with the opportunity to discover a major story in the history of teamwork and technology. In the…

Hi @shankhanath raychoudhuri and welcome to the Community! To be honest, it would be much easier to get this done if you would use a company managed project. Company managed workflows allow you to define a screen that pops up on a workflow transition and that would allow you to let the user simply select the new assignee.…

Hi @Paula Manildi, No, the team field is not multi-select. But an epic normally consists of multiple tasks / stories / other issues that can each be assigned to different teams (one team per issue). That way you can still leave the execution of work in your epics to the different teams involved. Hope this helps! 

Hi @marco_burboa and welcome to the Community! Could you provide a little bit more context to what you are trying to achieve? Assuming that the panels you refer to are Jira boards, I understand that you you have 2 teams. The team with access to project 1 can also access the issues in project 2, but not all people from team…

Hi @Sanjog Sigdel, As the error message says, Jira does indeed not support history searches on the sprint field. That means you cannot perform searches like WAS or CHANGED TO etc. on sprints unfortunately. There is a feature request for it that you can track here: JRACLOUD-39256 (it's a very old one, so I would not expect…

Hi @Maesaroh and welcome to the Community! Yes, you can upgrade just Jira Software to the premium plan while other products stay on the current tier. And yes, you can embed Advanced Roadmaps plans into Confluence Standard. Upgrading Jira Software to a premium plan does not affect your other products in any way. It just…

It is possible that you will see multiple in progress statuses in the list of available statuses, where you must select the right one (when you try to automate the transitions in your team managed project).

Hi @carolina, you simply cannot apply a workflow from a company managed project to a team managed project. They are different things and not interchangeable. You still have defined your automation rule too openly. The way you have set it up still allows any transition from any project to trigger a transition in the other…

Hi @carolina, The essential difference is that one project is team managed and the other is company managed. Everything you say is correct. Statuses is a team managed project are available in that team managed project only. Even when you would have 2 team managed projects with statuses with exactly the same names, they are…

Hi @bmccarthy, Yes, archiving is essentially somewhat like hiding a project so it doesn't interfere with your "active" projects. They stay in that archived state until you either decide to restore them or actively delete them yourself. Hope this helps!

Hi @Stephan Lewis, You can perfectly use greater than or smaller than with issue keys, like this: Project = IOS and key <= IOS-1000 That would return the first 1000 issues. And the following: Project = IOS and key > IOS-1000 AND key <= IOS-2000 would return the next 1000 issues. And so on. Hope this helps!

Hi @Afrothiti Manolis, As you can see in your first screenshot, the rolled up date you see there is displayed in italic. That means it is a calculated value you see on screen. It is not persisted in the Jira database and it is calculated dynamically based on the child issues you (don't) see listed under the > levels of the…

Hi @Dean Shirley and welcome to the Community! Long story short: all date fields you mention are just custom fields used on issues. If you use different start and end date fields in the basic roadmap vs advanced roadmaps, you end up with 4 date fields on your issues. From the field names, you may get a different…

Hi @Shubham R and welcome to the Community! I don't think that is going to work very easily. In order to do what you are after, you should be able to filter for issues that were in a certain sprint, but then later on were removed again. Since JQL does not support history searches on the sprint field, there is no supported…

Hi @RAUSHAN KUMAR GUPTA, Yes, possibly. To be able to identify this, could you share what you were trying to find and what the unexpected results were? 

In terms of news, it would be hard to top the Atlassian Intelligence (AI) announcements. But apart from that, I had an awesome time meeting fellow leaders, other partners, fellow country mates and the most amazing folks I hadn't met before. Inspiring as always and despite the fact that there was no official Team '23 event…

Hi @Frankyzhou and welcome to the Community! The control chart gives you insight in the lead and cycle times of the issues on your board. Have a look at this support article to learn more. Hope this helps!