Kit Friend Community Champion

@Changlin S clearing the sprint data etc probably won't give you great insights here (and you'll lose historic data being easy to see). The velocity chart does show you planned vs completed which gives a good insight on this: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/ You…

Hi Sam, Can you share: - What issue sources have you configured for your plan? This needs to include projects, boards, or filters which pull in all of the issue types you want to see - what hierarchy have you configured in Plans? If you are nesting Epics under a Feature, these will need to be configured to suit. 

So this intended to be a feature not a bug - it serves to show you which tickets have been carried over and which sprints they historically belong to. You could look at triggering an automation to clear this but you'd be losing useful historic data to help you identify trends in tickets rolling over etc. What problem is…

Change your incoming board filter so it's sorted by due date e.g. project = "Mobile Dev" ORDER BY duedate ASC

Server is end of life @shivani shirguppi - you'll need to migrate off it asap. 

Use Automation for Jira :) https://confluence.atlassian.com/automation/ You'll want to get off server asap though... it's end of life

Thanks @Ste Wright that's the page I got stuck at before tbh. My understanding of that page (and the config) is that it works well if I want to say "let everyone from @test.com sign up themselves" but (I believe) it doesn't stop people from other domains being added. My use case is basically that I want to stop admins…

Hey @brenna.oricoli Welcome! 1. Yes probably one per roll out is worth trying - Jira Releases are a fairly blunt tool though so give it a go without committing to that being the forever approach. 2. Yes - you can search and bulk edit, or (even better perhaps) create an automation rule that inherits the releases from parent…

I liked the boats and boxes - you're right it's not very consistent as a UX though. If your sprints work I'd definitely try that - best to keep things simple until there's a benefit to adding complexity :) 

Hey Terry, JPD is really designed for the initial funnel and high level roadmap view - for linked work and bugs etc you're better off planning them in Jira Software using the linked Delivery ticket functionality - the source of truth for capacity planning etc should be there. On some clients we've triggered the automated…

@christopher thorndike are you definitely using Jira Server not a newer version like DC/Cloud? Using the timeline or Advanced Roadmaps (plan) view is a good way to do this visibly. "Milestones" isn't really a concept in Jira but you can query what issues/tickets are connected to other tickets in a variety of ways. You can…

Nope, not really, and certainly not out the box without apps/plugins. What's the outcome you're hoping to achieve / why do you want to do this? There might be a better solution.

Hey! You won't be alone but there's probably some approaches which will make things easier: 1) Advanced Roadmaps works by creating 'cross-project releases' which... cunningly... sit across projects :D - https://confluence.atlassian.com/jirasoftwareserver/releases-in-advanced-roadmaps-1044784195.html - you can use this…

What's the usecase you're trying to accomplish? Having the seperate issue types in seperate projects and restricting access that way would normally be more straightforward than using a script. 

Jira, Confluence or both? Original post said Confluence... The python approach from @Sayed Bares [ServiceRocket] sounds worth trying for Confluence but depending on your answer I suspect there's a few plugins that can help you do a quick check and balance. 

It's just server that's EOL (Feb 2024): https://www.atlassian.com/migration/assess/journey-to-cloud

You're looking at the DC/Server documentation for Structure there Best to review Cloud docs if that's what you're using as indicated by the tagging here: https://wiki.almworks.com/documentation/structure/latest/cloud/progress-column-130883892.html 

Yep you can create lots of fields :) The synchronisation to Service Now is the tricky bit here - how are you intending to do it? What's the benefit of having any of the process in SNow vs having everything in Jira? 

Could you clarify what the outcome you're trying to get from the list is @Fuad Yatim - what will you do with the list once you've got a CSV? This will help us answer the question best :) You can see a list of projects by clicking the Projects button at the top and then All Projects at any time. In terms of 'space…

@Bill Sheboy I've been getting a (low number of) persistent errors where if multiple mentions are on the same text line without spaces or any punctuation between them, the amended rule fails. Did this come up in your testing? i.e. this works fine: but this fails: 

This is a long running challenge for teams seeking to use SAFe-type language in Jira which is somewhat fixed now in DC but not Cloud. The simple option is not to use Features as an intermediary layer - adopting a hierarchy like TIES (Themes > Initiatives > Epics > Stories) works great for many teams, and is a natural top…

It's normally set to hide only completed issues older than X weeks - this also relies on your workflow setting the resolution 

Happy to help :) 

If it's for one specific epic, you don't need the branching. Take out the branch in the above and it should work fine.

Yes - check what screens your project is configured to use and make sure the sprint field In company managed projects go to project settings -> Issues -> Screens and check the screen associated with creation In Team managed projects go to project settings -> Issue types and check the fields associated with each ticket

It should search all fields as long as the user has relevant permissions (normally Browse) for those issues. Can you provide a specific example of a search which isn't yielding the result you'd like but where the user can see that issue when accessing directly?

Hey @agrtechnology The simplest approach here would just be to setup your jira issues for the relevant projects so that the fields are the form you want their information inputted into - just configure the create screen fields to contain the questions and options you want. You could also explore Jira Product Discovery's…

And which is configured as the issue source in Advanced Roadmaps - the Board or the Project? Also worth reviewing the exclusion rules configured on your plan (see plan settings)

Sure - but understanding the outcome (what do they hope to use that data for in future?) helps shape the best solution :) 

@Vishal_Kalavar check what issue source you are using in Advanced Roadmaps - if it's a board (rather than a whole project), check that the stories you are missing appear there. The Filter at the top doesn't really relate to the plan (unless it's the filter driving the source board :) )