Comments
-
Plain Jira rolls up the estimates and includes worklogs, that's why your issues are able to display a roll up. But Scrum estimates should not, so scrum related functions do no roll-up. Your product owner does not care how you do the estimates or what your progress is - a story is either done, or it is not.
-
To get to the bottom of this, you will need to compare your backlog items to the CSV export items, and there are some quite random questions to ask: * How many issues do you have in the backlog and how many do you get in the CSV? * Are there subtasks in the CSV? * Is the backlog over 1000 issues? * Are you definitely…
-
Sub-tasks are not supposed to be estimated in Scrum. Your product owner ranks stories, and you tell them how much you are committing to. They have no control (and in theory, no interest) in sub-tasks, the only measure is "is my story done or not?" - Either you've completed the story (under, over or at the estimated level),…
-
Confluence doesn't have workflows, so I'm not quite sure what you are asking for. External tools with workflows could use the REST API in Confluence to add or update data in it, and if you got one of the workflow apps for Confluence, some could be configured to update data as well.
-
It's in the project settings, you need to check that the issue types use the same workflow and configuration scheme, and then also that they have the same custom field contexts from admin -> custom fields.
-
There's a couple of things wrong here. First, a new issue always takes the next free number in the project, you cannot set issue keys. (You can give Jira the issue key, but that tells it "edit existing issue if there is one") Second, your issue keys are invalid so it can't work anyway. Sub-tasks belong to parent issues,…
-
Again, quick filters are for temporarily narrowing a board to a subset of issues. The order in a quick filter is ignored because you are supposed to be using the order chosen by the board filter.
-
As a Jira admin, change it to read/write. You may need to talk to the admins of the directory - that could also be read-only, and that will need updating to allow Jira to write to it.
-
You will need to describe more of the problem. We can't see from this what "link additional info" is, or what is disappearing?
-
This has been discussed several times, and when Atlassian have spoken about it, the response boils down to: * It's complicated and hard to fix (i.e. expensive) * It only affects a tiny number of people - inexperienced administrators who don't know that they should always add at least one outgoing transition to every…
-
Because a LOT of people who set up mail servers use additional parameters.
-
Nope. Atlassian expect you to do project -> sub-project with components
-
I suspect you only have Jira Software installed and licenced. To change the project type, you have to: * Have a licence for some Jira Core people * Have agent licences for, and installed, Jira Service Desk * Not be trying to change a "Next Gen" project (these are Software only)
-
There is nothing more I can help you with directly. It's no good saying "no one is removing issues from sprints" or "no one is deleting sprints" - someone is. There is nothing in Jira that would do it without a human triggering that action. (Although, it may be automated or scripted, it is still initiated by a human) You…
-
Listener, not a post-function (you need a listener because the "move" function does not have post-functions. You could also construct a scripted field that reads the history and returns the old issue-key. You'll need to think carefully about what rules and display you want for cases where an issue is moved multiple times.
-
For those of us on server - you have to clean out the project table and the "moved issues" table, which means you lose a chunk of history.
-
This is a global setting, not a project or workflow one. (Kind of makes sense, as it keeps the UI consistent between projects)
-
There is something very very broken here - the 1 and the 15 in the irrelevant column should always be hyperlinks - that's the whole point of the gadget! It makes it impossible to diagnose further, but there are two more things to try. Could you Re-index the project and check the 2d gadget again? Run the integrity checker…
-
To do scrumban, start with a scrum board, and don't use all the functions.
-
Yes, it was closed ages ago with something that can be summarised as "saved filters are JQL"
-
You need to use web-links when pointing to an issue in another system - issue links only function locally within the current system.
-
Boards are a view of issues, not accounts. This means I do not understand the question: "Create a single view of different accounts" - you create views of issues. The accounts are used to log in. Could you explain a bit more what you are looking for? Maybe from your people's point of view - what are you hoping for (say)…
-
Er, the docs on "configuring the dashboard"?
-
It depends on the gadget you're using on the dashboard. Some of them work with dates and allow you to choose which ones. Some have hard-coded dates (because they don't need to ask - for example the "created vs resolved" gadget has no reason to use other dates, the hard-coding of "issue created" and "issue resolved" does…
-
Not quite sure what a scrum qualification has to do with this old thread, but I'm already a Scrum Master and I know Steve works with a lot of Scrum teams (I don't know if he's got certifications, but I would not be at all surprised to find out he's even better qualified than me)
-
I'm sorry I'm slow - last week was hectic at work (and short due to holiday), and this week it's Atlassian Open, so I'm in Vienna and talking instead of sitting behind a computer. The screen shots you've given us are really useful, but they're also inconsistent. It is like you are looking at two different things, but it is…
-
What exactly are the symptoms of the problem? Does it tell you it has changed, but nothing has? Or is there an error when you try to commit a change? Or does it not even offer you the option to change? What user directory are you using (internal, LDAP, Crowd etc)?
-
This will happen in two similar cases. The error message is correct in what it says - either there is a page with that name in the space before you begin the import, or you have two (or more) headers in the doc with the same name, so it's creating one and falling over when it reaches the duplicated name. You have a couple…
-
Atlassian has a very large backlog of requests, and obviously, some are more popular than others. They've not closed this request, so yes, they are interested in doing it, but when it gets done is dependent on how important it is compared to all the other requests.
-
Agile tends to suggest that testing should be part of the team capablity and hence estimated as part of a story. An estimate of X story points should include the effort needed to create and test the solution to the story. Because the testing should be part of the story, with test capability in the team, there's no need for…