Comments
-
The usual culprit here is that you installed it and ran it with a dedicated user (As you should), but on the penultimate restart, you started the system as another user (probably an admin) That user took ownership of a load of files and directories. Then, on the last restart, you went back to the dedicated user, who no…
-
Ok, it's on screen, so the next two questions are: * Are you using that screen for issue edit? * Do you have the project rights to edit the reporter? (Are you in one of the two roles in the project that have the right in your screenshot?)
-
No, because it is too late in the process, and there's no use for it. A transition is a broadly linear process - check if you can do it, user triggers it, screen appears, validation gets done, post-functions run, then status is changed to the target. At the point where the screen is presented, the user only has two logical…
-
You can edit the workflow, but when a workflow has that tag, it usually means it is a Jira Software "simplified" workflow - these can be edited by board owners, not just admins, and their edits can easily destroy any changes you as an admin might make. Unless you are sure this workflow has been de-simplified (the basics of…
-
When you say "move", do you mean you simple want to drop ABC and transfer everything to XYZ? To do that, you can now get Atlassian to change the ABC part of the URL. If you want to do it manually, you can take a backup of ABC (from admin -> backups), download it, then restore the file in XYZ. This will overwrite everything…
-
That is not a question we can answer for you. Some one in your organisation has decided that the two status are needed in your workflows and hence set them up. My guess is that they were thinking that they wanted a clear difference between things that had been raised and not really looked at, and things that had been…
-
Any other port that is not in use for something else! I would also consider using IIS as a proxy, so that the users won't have to use the port in the url as well.
-
OK, they do have it already - https://jira-software.status.atlassian.com/incidents/37qyptb43svr
-
You will need to talk to your administrators to discover what has gone wrong and they should be able to get you back in. We can't help you with emails or your Confluence directly, only guide you, as we have no access.
-
Not directly. In general, an edit on a page (or attachment) is for that page (or attachment), there's nothing that would duplicate it. Confluence re-uses content by using "include". If you need something to be repeated, then you do not copy it, you should have one single source of the stuff to be repeated, and use the…
-
You can't do this in native Jira. It has no field level security at all. You can stop people attaching files based on groups or roles etc, but if someone can see an issue, they can see its attachments. You would have to write your own implementation of an attachments field to do this. I've not seen anything in the…
-
What are you trying to achieve with this? I ask because the use of SQL against a Jira database is almost always the single worst way to do anything useful with it. It's complex, messy and there is almost certainly a better way to do it (in this case, why don't you just read the list of field configurations in the admin…
-
Ok, imagine you are the space admin, and you have a space you do not want shared with everyone. I'm one of your page authors, I have no idea about your rules on sharing, and so I can now let my friend in another department see it, without your knowledge? That's what you've just described - a complete loss of any level of…
-
Ah, right. Yes, that is correct, I expect it to move the four that are not "done" because they're not in the "done" column on the right.
-
Ok, I would be very worried about the "hibernate" error - that's saying "I can't get a database connection" You'll need to check everything about th e connection to the database!
-
Ok, I think there's a bug in the "look at this issue list" function there, not the JQL the gadget is running. What we need to do next is go back to what does work. Could you give us the board filter, and then give us the numbers of how many issues it returns in each status when you add "and in sprint 'PBFF Sprint 39"? (An…
-
It looks like it can't write to the disk properly. Check there is enough space and that you have permissions to read/write in there. If that looks ok, you'll need to consult your operating system logs to see why the writes failed.
-
Next-gen projects do not yet support sub-task types.
-
Sort of, if you're willing to do some code. See https://developer.atlassian.com/server/confluence/lucene-boosting-strategy-module/
-
Not really. A build minute is a minute spent by a pipeline building whatever you've configured to be built. For example, if you have a project which typically takes 4 minutes to do a build and you run a build 6 times a day, you will consume 24 build minutes a day. The usual (distant) relationship to a commit is simply that…
-
Ah, ok, you've lost your database. There's no point in recovering most of your data directory, the database is where all the bitbucket data was. Your git repositories are ok though, they live in the data directory, so you'll need to install a new bitbucket, point it at those old repos and reconfigure everything you lost…
-
This is a bit blunt, for which I apologise, but "I want to add "resolution" field to "default issue screen"" - no, you do not. If you put the resolution field on a screen that is an "edit" screen (i.e. create, edit or transition screens), it will get set. It's usually wrong to do that on edit, and almost 100% wrong on…
-
You don't tell the workflow, you do this in the board. Jira Software considers the last column on the board, on the right, to be "done". It does not look at the various status directly, you have to map them on the board.
-
You can use many "include" statements on a page too.
-
No, the only way to re-arrange the fields is to hack the code that renders the view screens. The only way to have fewer fields in one go is to use tabs.
-
Because it is up to the space administrators to decide who can see something. Your system would enable anyone to grant access to anyone. The reason it's done this way is simple - there's no coherent permissions if you don't do it this way, you might as well just grant view to the whole world automatically.
-
It's the "done" column definitely. The issues it wants to move to the next sprint are not going to be in the "done" column. My guess on the 4/7 split is that your tasks and defects are sub-tasks, so they follow their parent into the sprint (or not) and the sprint close report is ignoring them.
-
https://support.atlassian.com/contact I've asked informally as well, they may already have it logged/known
-
I think it's based on what column the issue would be in if it were on the board. What are the status and type of the 7 unclosed issues?
-
You are not the first person to report this today, I think the latest Cloud update has broken something. This needs to go to Atlassian as a new bug.