Comments
-
Yes - create an issue type of sub_bug and add it to the issue type scheme.
-
Make sure the "done" state is in the last column on the board. How you decide an issue should be in that status is up to you though. Jira just takes "in the last column" as "done".
-
That's one of the best, yes. Sticking with the analogy, the person working through Box C finds a really shiny thing and the others agree it's far more important than Box B or anything in there. They'll need to discuss whether its best to put it in the list between A and B (convert it to a story-level issue) or move it into…
-
I'm afraid this is technically the correct behaviour, and Atlassian are unlikely to change it. The underlying concept is that sub-tasks are part of their parent issue, not (semi) independent objects. Imagine you've got three boxes that have several objects in them that need some attention. You decide Box A is the most…
-
You have two options: * Go up through the page tree to the point where you find the page providing the restriction, and amend/widen it or remove it. Bear in mind that will affect all pages beneath it, not just it and your page. * Move your page from under the page that is holding the restriction to somewhere that has the…
-
You probably want to use the system user, rather than root.
-
Ok, that's just the usual culprit, we'll need to dig more. What are you defining as "done" here? Do you mean it is displayed struck-out, appears in the "done" column on the board (farmost right one) immediately, or it has a status of "done" (or closed or something at the end of the process)? Or a combination of some of…
-
If you find one in the directory that fits what you're looking for, then they all have contact details behind the links to their sites. Most of them have websites on the most obvious domains (e.g. Deviniti.com, Adaptavist.com, etc) , which has contact details and their preferred routes of reaching out to them. If you were…
-
I haven't looked, I can't remember the exact synonym for "configure" that Trello uses. Customise or Settings maybe? Probably in one of the settings or profile menus
-
From someone with 16 years of using, deploying and supporting Jira in large development environments, and seeing this sort of thing causing all sorts of problems, I'm speaking from experience. Seriously though, the main problem I've seen is when people try to do this sort of thing, they fail to consider others around them.…
-
There's a lot of software out there that can meet that use-case. I'm not being hard on Trello, it's really good at what it does, better than most. But I've got three other apps on my phone alone that can do the case presented.
-
No, the "scripted field" is showing 1897 (seconds). The source field (which is not the scripted field) is showing 31 minutes (or 1897/60 rounded down) That's not what you showed us before. However, it is now showing correctly. Your script is returning a simple number which can be cast to a string automatically. The script…
-
I'll give an example: I put a label on ABC-123. Later, I go to a dashboard that displays labels. You, as the author of the board, has decided they are not interested in the label. They have arbitrarily removed data I expect to see and should be there. You have arbitrarily dropped something I want or expect. This is less…
-
Start at https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/
-
There's nothing to "fix" there. You have set the reporter mandatory, so you need to fill it in.
-
SQL is a last restort, the worst possible way to get information out of a Jira database. You really should avoid doing it this way. However, if you insist, you'll need to * Read Project to find the project ID * Read nodeassociation to get the workflow scheme for the project * Read workflowscheme to get the workflows…
-
So, it's not giving you what you have in your screenshot ? It's giving you a properly formatted number?
-
Ok, well, this does not look like what scriptrunner would do given just the lines of code you've given, so I'm a bit stuck. Could you give us the rest of the script?
-
Yes. Do you have soething to actually talk about?
-
What version does the issue say it is fixed in? And is your version affected?
-
I know that, that's why I gave you the code to do that.
-
You should do what it says and check what the application logs say to confirm exactly what went wrong. Start with <confluence home>/log/atlassian-confluence.log "Cannot update schema" though strongly suggests a problem with the database. The application log will tell you the details of that, we can't tell you a lot more…
-
Yes, probably. Could you explain what you mean by these two statements?
-
I suspect this is because the first clause could be pulling in issues from all sorts of places (even if you don't have data that would do that, it could do it). Project DCE might have one or more issues with "Epic Link = <an Epic in another project>" Normally, you wouldn't draw Epics into a sprint, so I wouldn't be trying…
-
There is no need to mess about converting to strings to do this comparison, and in fact, this is making it worse for you because you're comparing things that you've cast and not fully understood the results of the cast. The most simple structure you could use here is: def due_Date_1_value = issue1.getDueDate() if (…
-
Your script is returning a number into a string field, so the field doesn't really know what you're trying to tell it. My best guess is that your script should to changing the number returned explicitly to the string you want to see, but it is an odd conversion there, not what I would expect. We don't know what tool you…
-
Yes, it will! That's actually what the software was designed to do, although I don't think it is obvious that that is the case!
-
No, it is correct. The estimates are for an issue. One reason is works this way is what sub-tasks are for in Scrum - nothing. In Scrum, you commit to doing a set of stories in a sprint. You can break them up with sub-tasks if you want, but those are irrelevant to measuring what you deliver during the Sprint - burndown and…
-
Have a look at the main "create" process (Click "create" from the menu and select the project and issue type this is happening with). Does that screen have the Resolution field on it?
-
Ahh, the perils of estimating on sub-tasks! In both of your examples, the display is correct. The important piece here is that the estimates are for the issues, not the person the issue is assigned to. Let me explain by re-wording your first example a bit: Example 1: Story ABC has two subtasks. There are 0 hours logged for…