Nic Brough -Adaptavist- Expert

No. This is wrong. You can not change the names of groups this way.

Welcome to the Atlassian Community! I very strongly recommend that you do not do this. The Jira database is not intended for any form of reporting, it's a data store for the application. If you go down the route of reading the database, you will be making a world of pain for yourself. At best, you're going to be spending…

You can not "edit" a status. The only way to change status is to use a transition. I'm afraid @Robert Wen_Cprime_ 's suggestion is wrong - if you use bulk edit -> edit, you will, and already have, find that the status "field" (quotes because it is not a field), is not offered as something you can edit. But you can use bulk…

Quick filters are for drilling down into a board, they can not amend the board filter. You can use your filter as the board filter, but if you do it, you will lose the ability to rank issues in the backlog, because you'll not be using that to sort it any more.

Welcome to the Atlassian Community! Jira does not have nested projects, each one is an independent entity. So issues created in your new project will not affect any reporting you are doing on the existing project. Jira's dashboards are user-created reporting screens, they're not part of a project or board. Most of the…

Welcome to the Atlassian Community! My guess would be that "part name" is a string field (probably short text). These fields are not usable in the two-dimensional gadget because the range of values cannot be counted, it's not a bounded list. It would not be of a lot of use in the gadget because it would simply have one…

Sorry, I was not clear. Can you show us a screenshot of one of the issues, one that includes the status field?

Because I've been working with loads of people who use this type of software for over two decades.

I forgot, the permissions to check are "manage sprints" and "schedule issues"

Confluence doesn't have the concept of a page "owner", beyond it being "anyone in the team who can create and edit content in this space". That makes me have to ask for some clarification - what are you doing to represent "owner"? Are you assuming "author" (the person who first created the page) is an "owner"? Are you…

Welcome to the Atlassian Community! Not just page creation, no. If someone has permission to create/edit in a space, then they can create a page anywhere in the tree. If you use restrictions to control who can edit a page, I think that stops people creating beneath a restricted page, but I have not tested that recently, so…

I'm afraid it's not in DB, they're generated on view. You probably should not be looking at the database, it's not got everything you think it has in it, and it's not a sane place to visit for reporting.

This would be done in the field configuration of the target project on the issue level, and in the request definition. You'll need to check both.

Could you show us the workflow and the board filter? Also, your status is cut off at differing points, so I'm wondering if we might be seeing the right one. Could you visit admin -> issues -> status, and go find the "selected for dev" status - look above and below it, are there others? For example, I ran into a place a few…

I am sorry, I do not understand the problem. If you have removed some status from the workflow, then issues that are in that status can not have that status any more, because an issue has to be in a status in the workflow to show where it is in the process. When you migrate to the new workflow, Jira asks you what status…

Welcome to the Atlassian Community! Yes, this happens when the target project and issue type are configured to have mandatory fields - the move process checks that the data on the issue is valid for the target configuration. Note also that if you have fields that do not have a context for the target project, you will lose…

So the issue is not Closed?

That means your admin role has permission to manage sprints, but ordinary users do not. That's the only way to get what you are describing here. Check the permissions on your project, but also have a look at the workflow - you can change permissions by putting properties on the steps in the workflow.

Go to project settings -> Issues -> screens, and you'll see a list of screens in use for most actions on the different issue types. Find the screen mapped to "create" in there and click on the link to it. You will land in a screen that allows you to add, remove, and re-arrange fields.

I can't help you if you do not describe the symptoms. What does "can't assign issues" look like?

Welcome to the Atlassian Community! Whilst you can choose first-name, the rest of your URL is fixed if you use Cloud See https://jira.atlassian.com/browse/CLOUD-6999 On server/DC you can do what you want - it's all up to your network team to define URLs for access.

We just had a request similar to this go through our "Assist" service. I know that is an advert, but I am hoping you might see it as an example rather than an ad. Bob (name changed for privacy) created 30 custom fields, adding all the needed options to the ones that were select lists, then the project, then the 22-step…

We all like the swags ;-)

The native time-tracking works the same in all of the three project types (Work Management, Software, and Service Management). I am not sure about Product Discovery projects, I have not yet spent much time in any of them (in curious digging mode, let alone "production") But the native reporting on work logs has been simple…

I am sorry, I was very unclear in my request for more information. I would like to see the profile of a user that places them in one of the groups in your screenshot, and to see the options on an issue on which they cannot log work, where the issue has them as assignee or reporter. This can be done in one go if you open up…

Welcome to the Atlassian Community! No, that is a ridiculous estimate, an experienced Jira admin could probably do most of that in under an hour (the exception might be the import of issues, depending on size and complexity)

Welcome to the Atlassian Community! If your CUI is a file, then yes. It might help to explain what you mean with that TLA - Concordia University? Single integration contract?

It is not hard to set, you have it all set correctly already. I think we need to check the user who is not getting the "log work" option against the issue they are trying to log work on.

Have you restarted both Confluence and the database server to pick up the new settings?

Ok, you've found the wrong documentation, you're looking at Server documentation, while using Cloud. As it says in the screenshot, if your people can't see a log-work option on an issue, then they do not have the "work on issues" permission in the project. You'll need to enable that for them to use time tracking.