Comments
-
It doesn't. See https://confluence.atlassian.com/agile067/jira-agile-user-s-guide/jira-agile-tutorials/tutorial-planning-and-estimating-work-for-an-agile-team
-
>It’s a pity that sub-tasks aren’t visible during Sprint planning Sprint planning is about getting your backlog in a ranked order and building a sprint goal for the next sprint according to your capacity. Sub-tasks are not needed in sprint planning because they're useless there - it's nonsense to rank them outside their…
-
Ok, I'm really not sure why this seems to be so complicated. Because of your questions about how "tasks" should interact with your stories, I think I've been focussing on sub-tasks, where all of the stuff about breaking up stories and estimating does matter. So, I've misunderstood what you're questioning. For that, I do…
-
Ok, the sub-tasks shouldn't affect your velocity. They're there to break up stories into smaller pieces for a number of reasons, but the story points are on the story. If a new task is a new piece of work that you have to do, then there are a couple of options. If it is definitely part of an existing story, then add a…
-
Sub-tasks are a handy way to split stories up when they need to be worked on by more than one person, or just when developers feel that it's useful to break it up in to components. I'd skip the estimates on them - the time tracking is useful for logging work, but, as you suspected, not estimates. (By the way, "Based on the…
-
As Jobin says, there's a request open already. I usually find requests for defaults or templates tend to mean there's something broken though. If you're trying to default things like description or short and long text, then you've probably got a broken process. If you're trying to default dates (e.g. default deployment…
-
There is a difficulty here. In a lot of cases, validators are simple. "What is the flight speed of an unladen swallow"? The answer is mandatory, so you can and, exactly as you say, tell the user that somehow (like the red asterisk) But it fails for more complicated validators. Field is mandatory is one of the simple cases,…
-
I'd like the red * to get rid of the handful of "it didn't tell me" complaints, but as someone who has used JIRA for <mumble> years, I don't really care. I fill in the fields I think I want to, click go, and when I miss a mandatory one, it tells me (unless the admin has set up a bad validator that doesn't) Totally agree…
-
Indeed. I don't quite understand "I don't want to use the method that is designed to meet this need, and is the only way to do it"
-
Ah, I see, this one: https://marketplace.atlassian.com/plugins/com.drunkendev.confluence.plugins.attachment-tools-pluginAfter you configured this, have you left it to process? The job that removes older version runs at midnight (by default - you can change the time), and you need to let that run before you will see the…
-
I'm sorry, the question is not clear to me. What addon are you using, and what do you mean by "manage page version"? What are you expecting to see on this page and what is missing?
-
Ah, yes, good point, they need to be reassigned (or unassigned) You can stop them using a license seat by removing them from jira-users though...
-
There is no screenshot :-( (Answers does this to us a lot, not your fault) It's almost certainly one of your adminstrators creating a dummy account - go into the list of users - if "unassigned" is in there, then it's a real account and you should delete it (or at least rename it to "dummy account for unassigned" for…
-
If they don't have accounts, then the only option is to grant anonymous access, which will let everyone see it. Check the permission schemes for the projects you want to make visible and add the group called anyone to browse project. As you've already suggested, I'd advise using this only for browse project and nothing…
-
No, plugins are installed globally. Some contain limiting code that can restrict them to working on chosen spaces, but that's a function of the add-on.
-
No problem. Blocking 8080 is weird, but fixable - you could fire up a proxy on the server that accepts incoming connections on a different port and pushes them to 8080 locally. Or just tell the provider/firewall that they'd doing something wrong and you need it fixed :-)
-
Not inside Jira - it doesn't do ip-blocking, let alone the geo-ip location for identifying where people actually are (well, not "are", but "might be" given that there's blocks of German IPs in the UK, and several UK ISPs sometimes relay through Denmakr). You need to raise this with your network (or possibly server) support…
-
I think this sounds like a job for Webhooks
-
The upgrade process tries to do an export of your existing data before it tries to upgrade it. This process is failing because you have one or more add-ons in the 6.3 install that are not in your 7.1 installation - the backup routine is trying to export their data, but can't do it because it doesn't know how to read/write…
-
So look for affects-version 5.2.4 and read through them.
-
I'm not sure what you mean by "open issues between releases"? Do you mean you want to know what new issues were raised against a new release? I'm guessing you probably need to simply use "affects version X", where X is the version (or string of versions) you want to know the bugs were found in?
-
See http://jira.atlassian.com/browse/jra The release notes show you what was fixed in that particular version. It's not going to list all the remaining outstanding issues because, well, they aren't fixed, so they're not in the release. There are plenty of open issues between releases. Many are feature requests. Some are…
-
I don't think it's as simple as that. At the point that the validator runs on "create", the issue has not been created, so your code is fetching a 0 as it's not there. I'm not sure, off the top of my head, how to deal with that.
-
You'll need to find or write a validator add-on that can check the number of attachments. It's a doddle if you've got something like the Script Runner add-on.
-
I think you've hit a JIRA bug, which does not yet have a fix - https://jira.atlassian.com/browse/JRA-63363
-
I'm afraid I only know of one way to do this in Jira 3.x * Stop Jira * Take a backup of your database * Prove the backup works * (Yes, I'm serious about backups, as amending a Jira installation via SQL is a recipe for disaster) * In the database, insert into fieldscreen values ('10031', 'Temp name', 'Temp description') *…
-
Ouch. I've done that in the past (it's nothing to do with "screen schemes" though, you've created a "screen", used it in the workflow, and then deleted it). It sounds a little odd to me though - I was usually able to get into the list of workflows, to have it crash out if you click on the damaged workflow. Are you really…
-
Define "attended to"
-
The edit allows you to change the logged time. You don't put in -15 minutes, you change it from 1 hour to 45 minutes.
-
There's no way to do this - the knowledge base search is based on trying to find similar text. There aren't any real rules for a drop-down list.