Nic Brough -Adaptavist- Expert

That sounds right. Jira will not let you delete users who are assignees, the reporter or have commented on issues, which solves most of the problems caused by deleting users, but it can only do it for the internal directory. If you're using any other type of directory (ldap AD, google, Atlassian accounts, Atlassian Access,…

Technically, I could say my main office is a few seconds away from home. When we moved into this house, I took over one of the bedrooms as a "study" and use it for work when I have a "work from home day". Those were once a week when we moved in, but well before Covid, I'd managed to flip it to "go to London once a…

On Cloud, your Tempo data (including the worklogs logged via Tempo) will be gone if you remove the app. Worklogs done in plain Jira without Tempo will not be affected.

Resolution is a system field, but one that is (effectively) handled automatically by team-managed projects. You don't add it and you don't need it in those projects.

>In team we have 2 scrum boards and creating story in project is seen into both the boards. Boards are not a container of issues, they are a view of a selection of issues. If an issue appears on a board, it is because the board filter has selected it. The way to stop a board pulling in an issue is to amend the…

You will need to get an admin to re-enable the account before you can re-invite it.

Ok, then I suspect that your board is not including all the sub-tasks for every issue in the sprint, and some of the ones not on the board are not complete.

Don't worry about the screens themselves to start with - look at the projects for duplication and simplification first. Change the screens used by their issue type screen schemes to take duplicates and unwanted screens out. Once you've done that, go to Admin -> Issues -> Screens for the list. This admin section lists all…

I'm typically about 100-120 minutes from any of the offices I've been based in over the last 25 years - they've all been in London, which is a 20 minute walk to the station in my town, then an hour on the train and then another bit of tube/bus/walk to Shepherd's Bush, the City, Southwark, Canary wharf, and most recently,…

>Team member 1 has access to project A and he should not be able to browse project B Check the permissions scheme. The rules in there determine who can see a project. For Team Member 1, give them "browse project" in project A, and do not give them that in project B.

Are all the sub-tasks in the last column on the board?

Could you show us an example of an issue that is showing in the filter that should not be? Just need to see the status, project and issue type "fields"

Could you explain what this has to do with Jira?

The application or page you want to embed Confluence in will need to support the authorisation that Confluence Cloud needs to let your users access the spaces and all the supporting javascript and css that Confluence uses to display things.

I think you've missed the point here. I can't think of another way to explain it.

Jira permissions are permissive, not restrictive. If you want to stop someone doing something, you do not restrict them, you remove their permission to do it. So, to stop team member 1 browsing project B, you need to look at what permission is letting them into project B and remove it. It will probably be a role or group…

Your people will need the schedule and edit permissions to do that. Those permissions will let them edit the issues as well as rank them.

That makes no sense, you should not be writing to a Confluence database (you probably shouldn't be reading it either - it's not designed for reporting either)

And how are you putting that into Confluence?

I did. It doesn't answer the question.

There's not a lot we can talk about until we know what data you intend to draw diagrams from.

No-one mentioned a tab. Try the operation menu next to each project.

Start at https://www.atlassian.com/software/jira/guides/getting-started/basics#step-2-pick-a-template

Indeed it is a risky approach, but "arbitrary flag to include something" is the only way to deal with the original questioner's case. The main point of "sprints belong to boards" is that they are not project artefacts. The board association is more loose, but that's where you create them, and if you kill a board, you lose…

So do I - there's no "hide field by person" in plain Jira, which is why I suggested apps. I'd want to experiment a bit more to see what you're seeing.

Oh, hang on, I see, you weren't talking about the way you have to create templates, you thought you couldn't create your own! You can add templates to the list in your last screenshot. Space administrators can go to Space Settings -> Content tools and see the list of templates for the current space, and add your own…

I can't see any apps in the marketplace dedicated to that, so you'll either be looking at building your own app or connection over REST, or using one of the more generic tools for connecting them (IFTTT, Zapier, Autoblocks, Scripting apps in Jira, etc)

Er, that's not a Jira function - it does not hide fields based on people. I suspect you have an app (like the Quisapps field security or Scriptrunner Behaviours) doing that.

Probably, but there's a lot of places it could be a bug, and you'll need to do some tracing. For a start, try a different browser - does that look the same?

I think you might need to look through https://help.nextup.ai/en/articles/4311885-configuring-fields-displayed-in-slack - I know the app supports creating issues with custom fields ("Severity" will be a custom field - Jira deliberately does not have it as a system field), but I'm less sure on how to display it where you're…