Nic Brough -Adaptavist- Expert

I don't understand what the video is trying to show us. It has nothing to do with your question about the filters.

Where was the database? (I.e. what type of database was it and what server was it on?)

You'll need an app that can insert a "web fragment" (unless you want to amend the code of Confluence itself). For a link like that, you'll probably need to write your own app to do it, unless you are happy to install one of the few apps that allows customisable web-fragments to be added (Scriptrunner is the only one I know…

For what it's worth, it's not a problem with Scriptrunner, it's the way Jira serves up field data to Confluence. That's why you got no traction with SR support - there's nothing they can do to fix it.

The releases are not broken down by what area they are fixing. Some releases may be just fixing a security issue. Some releases may be fixing a non-security issue. Some releases may add or improve a single function. But most releases contain many changes and a complete mix of improvements, new stuff, non-security fixes and…

There's only one called "Structure" - https://marketplace.atlassian.com/apps/34717/structure-project-management-at-scale?hosting=cloud

That's not a use case. The whole point of a field is that you want to report on it somehow. Could you explain what reporting problem you are trying to solve with this field?

Eh? How?

You need to compare the board settings (which aren't directly customisable) with the issues being added. What type of board (project) is it? Scrum, Kanban, Business etc? What status, fixversion and resolution does a new issue have? (One that does not show up)

Indeed - but a template doesn't solve that problem.

It's possible to do with Scriptrunner, but the script would be quite involved - it would have to run a search to find the current largest number, add one to it, insert an entry into the custom field options, then apply the new option to the issue. I would not waste my time with this. I would question the use for it. I…

A desire for templates in issues just screams "you've made your system too complicated"

This is because sub-tasks do not have an independent sprint field. This is technically correct - a sub-task cannot be in a different sprint to the issue of which it is a part, so there's no need for the sprint field to be on it. But it is annoying that it breaks reporting like this. You can usually spot a Jira I've been an…

That's incorrect. Jira Software only has levels of Epic, Issue and Sub-task. Stories are at the issue level, as are Tasks by default (but some admins rename Tasks and then create Task at a sub-task level) To get Themes and Initiatives, you're going to need apps to create the two layers above Epic. Atlassian has Jira Align…

Yep, on server, you can do it, but you need to mess with the database to fully remove the "hangover" project, and I suspect Cloud is doing the same thing.

Oh, and people should never be using excel for comments. It's a spreadsheet, not a story telling tool. They should be making comments directly on the issue, or providing simple text to be added to the issue. Comments should not be done in attachments, ever.

Yes, you're gathering information in the wrong way. The user's comments should be a set of comments on the one issue you should be using to track the work item. Why have you got 10 tasks for one item?

Any of your administrators could have added it. But go to "manage apps" and look for "audit log" at the bottom of the page. It should show all the installers. You will find some "anonymous" entries - these are either Cloud default apps added during the system creation or someone who has been removed from your system, so it…

No change so far.

I would recommend questioning what use the spreadsheet is. There is going to be a better way to do what is required than downloading copies of bits of issues en-masse.

Yes, with a bit of work on calculations. The files you'll find in the directory tree are the physical copies of the attachments you see in the UI.

There is no way to do this yet. Next-gen only relatively recently got the single type of "sub task" added to it

Exclude them from the filters you are using in the reports?

Jira Align is the usual recommendation here, but Advanced roadmaps and Structure can do this. I would recommend not trying to insert Capability and Feature under Epic though - Jira Software implements Epic -> Story -> Sub-task and that works fine, apart from having to use the name Epic instead of Feature. If you don't try…

I'm in a different team, but yes, poking the product team for support was going to be my next suggestion.

Nope, we can't. We're not Atlassian and hence have no access to the licencing system. You need to raise this with https://support.atlassian.com/contact

NO! You should never have a resolution of "unresolved". If you do that, you have broken all your reporting because you now have issues that are resolved and unresolved at the same time.

This can't be done, the code does not look further than the immediate layer. It wouldn't work on the most part anyway - most Jira systems have a group that says "can use Jira" and your reporter will be in it, along with everyone else...

How are you representing these "relationships"?

That's a browser setting usually.