Comments
-
You'll find some of it quite intuitive, and other bits not so much. I can't predict if you'll get stuck, or where, so I reckon it's better that you search when you do get stuck, rather than give you a pile of links that you might not need! "Configuring" is quite a good word to look for though. Of course, if you get stuck…
-
It depends on what you're trying to do. Try typing "configure <which bit you're currently stuck on>" into the search
-
That document already contains all the detailed steps, down to a level where you need to know the basics of JIRA. If you're missing the basics, then the rest of the documentation is well worth a read, especially configuring fields and configuring workflow
-
From your account at my.atlassian.com
-
Agile will make no changes to your data when you first enable it. It will add some stuff it needs to hold config for what you're going to do, but your issue data will be effectively untouched. Specifically, it won't do anything with your workflow unless you tell it to. Some of the project templates will create new…
-
The plugin doesn't have that option, you'd need to code and extend it.
-
Actually, that answer is exactly what I said already.
-
Remember to STOP Jira before doing that, or you may find it does some odd things.
-
You can't. You cannot know what the number is going to be until the user clicks the "save" button. Simple scenario - the counter is at say 576. So you start creating an issue. Your logic would say "the number will be 577". You don't type as fast as I do, and I click create before you. I get 577, and you get 578.Also, I'd…
-
You can stop Jira, set the counter for the project and restart it. Uses SQL, and I really do mean it about stopping Jira, so that might not be suitable. The other trick I use is exactly what you've suggested - import a CSV with the right number of lines, and then delete them all later. (Spreadsheets make it very easy to…
-
No, you do not "assign tasks to boards". Boards select issues from your JIRA. For an issue to appear on a board, it simply needs to match the board filter. Have a look at your board configuration, that will show you the filter. Then you just need to make sure your tasks match the filter.
-
So you're saying that the parent and subtasks have the same workflow?The only thing that stops transitions happening are the conditions on the workflow, or that the workflow does not have any transitions *out* of the status that the issue is in.Could you go to the plain issue view (forget the boards for now) and check1.…
-
Have a look at the conditions on the workflow for the parent issue type. I suspect you might find one that says something like "do not allow closure if there are any unresolved sub tasks"
-
Nope, still mice. Or better, Meeces, as I hate meeces to pieces.
-
You'll need to dive into the code to do this, they've been built as improvements adn no-one has anticipated any need to disable them. FWIW though, I wouldn't bother - they're useful for a lot of my users, extremely useful for a handful of them who can't use mice. I'm assuming you've got an edge case where removing them…
-
The off-the-shelf email handlers do not have the functionality to read and interpret emails like that. You'll need to find/write a handler to do this. I always look at JEMH for this sort of things.
-
Ok, so if you login as an admin, go to admin -> projects, there definitely is no project with a key of JSP? Two quick thoughts * have you had a project in the past with a key of JSP? * Could you check the regex - admin -> General -> Advanced, and see what the regex for prject key is? If none of that, then what does your…
-
Ok, the key is long enough, but have you checked the other two conditions in the error message?
-
Ah, you mean "where it has been referred to", not "where used" (because used might mean read by a human, edited, linked from, linked to, read by another system, and so-on). I'd mark Steven's answer right in that case.
-
What do you mean by "used"?
-
System usage monitoring and the logs are about the only way to find out what's going on here. We don't really have a lot about your configuration, what's running on the machine, what resources are in use. Have you tried debugging thread traces on the one that has "stopped working"? And when you say "stopped working", what…
-
Mmm, they are mentioned in the docs (e.g. a "small" Jira would run comfortably on most modern off-the-shelf machines with 2Gb RAM), but I certainly would not argue if you described that information along the lines "not obvious". It's there - https://confluence.atlassian.com/display/JIRA/JIRA+Requirements but I had to hit a…
-
Other stuff I'd probably do if I started getting complaints about not being able to create in an inactive project: * Change the project description * Move the project from its current category to a new one called "inactive" * Change the project name (So if you've got project "Dancing Badgers", you display the short name…
-
Create a new permission scheme that has "Create issue: <no one>" and apply it to the project. It's not a particularly visible flag, you just won't be able to create anything. I'd scan through the rest of the permissions too. It has an instant effect and is really easy to change back.
-
Sadly, some people are stuck with ClearCase, we should try to help them where we can (although we should always emphasise that migration to a proper SCM is always going to be the best option)
-
Yes, but I thought "you need to talk to an administrator" might be enough to tell you that that is your only option. Users can add/remove themselves as watchers on issues, and that's it. I'm sorry, that reads back as being terse, and I really did not mean it that way. Hopefully, you read it better than I wrote it. I wanted…
-
You need to talk to your administrators about the "notification schemes". (At the very least, I tend to remove the "tell everyone about issue updates", as those are usually overwhelming.)
-
The assignee is the person currently working on the issue. JIRA is very strong on having one person, as when you allow multiple assignees, you always get cases where someone thinks someone else is working on it, and your users simply don't know who to talk to about it. The assignee is expected to change over time,…
-
You could track the progress by having a "part complete" type field, or estimating in time and logging work, but that's not what a burndown works on. The chart works on the things completed in the sprint. If you do the "how complete is this" thing, it's fine, and there are some other reports that can help you visualise it,…
-
That's not how a sprint would work - you can't measure your actual vs estimates if you are adjusting them mid-sprint and expecting the burn-down to change. You have to complete an issue for it to count.