Comments
-
And how does that work with ranking?
-
Probably some nasty unsupportable javascript hack. Have a look at the global header to see if they've bodged something in there you can re-use.
-
There's a couple of existing requests in JaC for this, but they keep getting closed down because the people raising them can't define any useful scheme for what they want from the sort. What would you like to sort, and how?
-
There's no way to do this with plain Confluence. If you can see a space, it appears in the navigation elements because you're supposed to be able to see it.
-
Again, boards are not containers. If you copy a board, it's going to show the same issues as the source board, because it's selecting the same issues from the list. It's nonsense to expect a copy to "not have any issues" because you're copying something that is configured to show the same things. Please, think again about…
-
Don't remove any roles, just remove the default groups from the existing roles. That will stop the defaulting-when-new problem. Worst case, you can always put them back.
-
To be fair, you're now struggling with operating system vs required database problems, not Atlassian software vs OS or DB, and you can't expect them to document it for everything (there are 100s of Linux variations out there. My home systems have no problem installing postgres on a Pi). On the Ubuntu 18 I do have access…
-
In which application? JIra is the one which has a full workflow engine. For conditional flows, start with https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html and pay particular attention to "conditions" in the workflow.
-
Start at https://www.atlassian.com/software/jira/download
-
Go to Admin -> Project Roles and you'll see the global list of roles. (Use the admin search field, I can never remember which section roles comes under) You can edit them and set or remove any default groups you want. As you surmise, you'll still have to clean up old projects, but new ones won't be polluted any more.…
-
Have a look at the Jira application logs - it sounds like it has stopped processing the incoming mail, and there is likely to be an error message to tell you why.
-
That is correct, yes.
-
We can't see other people's support calls.
-
I think you can do this with the Jira macro - use it to filter for the list of issues you want to report on, and select the fields key, summary, status and progress. This was based on a quick look in Jira's issue navigator, where you can choose columns, including the progress one - that shows it as a percentage and the…
-
If you have a small instance of Confluence, there is a metrics app built into it, which you can enable to get some basic numbers out. It does not scale well though, and doesn't have a huge range of information. For larger instances or better analytics, take a look in the marketplace. There are several options, some which…
-
The workflow living behind the board does not have transitions from the current status of the issue to a status in the "done" column, or, if it does, you don't match the conditions set on it. Open up the issue in full and check the workflow.
-
Click on board configuration (it's towards the top right of the board). You have to be a board admin to be able to use it.
-
It's done in the workflow transition, not the screen. I can't remember the property that does it, but if you copy and edit the workflow that you see the box above in, you should find properties apply on the transition, which you can copy, paste and amend into your own workflows
-
It's something I suggest to people a lot actually. Use one scrum board as a scrum board, and then one or many Kanban boards to visualise and amend your data for other processes. One good example for me was a design company that did kanban/scrum/scrum/kanban. The first kanban covered new stories and a design phase, where…
-
1. Does not matter, the migration can be done before or after upgrade. 2. No. Well, it might work, as a 7.9 install will in theory spot the 7.0 data and try to upgrade it. Try. And, often fail. It's absolutely not the recommended route. I would strongly recommend following the upgrade docs - upgrade the system in place.
-
There is no change to the behaviour. For those of us using plain Jira (not doing sprints), the original estimate and worklogs add up on to the parent issues. For those of us doing sprints, you do not estimate on sub-tasks, as scrum only looks at the parent issues. In general, you don't estimate on sub-tasks because it's…
-
Boards are not containers for issues, they are views. The reason an issue is deleted on both boards is that deleting an issue deletes the single object the boards were looking at.
-
You've missed the line in the doc that says "group". "Anyone" is an option in the list of groups.
-
Yes, you'll get the screen pop up when dragging into Done
-
Those are operating system things, not Fisheye.
-
True, and the recommendation is that you upgrade to "latest". You'll need to go to at least version 6.0 before trying it, and I'd strongly recommend 6.6
-
There are no limits in the applications, you'll need to give the server or database more storage, or increase the user's limits (if quotas are in use)
-
No, you're not confused. It's always a good question to ask - how do we want to handle issues that don't lead to us doing anything. The best answer is still that you want to close the issue as Done, with a resolution that clearly indicates what you've done about it (Won't fix is good). This leaves you with clean accurate…
-
Yes, you're right about a retrofit. The way to solve this is to edit the workflow, picking the transitions that go into "closed" type status (ones in the rightmost "done" column) and either put a "screen" on them with the resolution (so the users pick a resolution) or a post-function that sets the field to a value. You…
-
There is no macro, it's a function in the editor that records and recognises dates.