Comments
-
Indeed, profields is an excellent way to add project-level data. I think Daphne needs to work out what she's actually wanting to search before she can decide how to approach the problem, but if storing data at a project level is the route, then I was going to suggest exactly this plugin.
-
Ok, I can see the problem, but I can't see how you expect a project search to help you. There's two questions here: 1. How do you know that customer X should be raising something in project Y? How are you storing that relationship? 2. Again, the question is how you expect "project search" to work? How do you know what you…
-
What do you expect a "search on projects" to be? I mean, what results would you expect? What does clicking on "projects -> view all projects" not do? Jira's searches are for issues, which belong to projects. You don't assign projects to people, you assign issues within those projects. All you need to do is run the standard…
-
No problem ;-)It's worth voting and adding a comment if you can though. Atlassian do consider votes when deciding what to tackle next (it's not the only thing they look at, but it is used)
-
Not a clue, I'm not an Atlassian, so I don't have any more information on development issues than you do.You should be able to comment/vote on that issue if you have an Atlassian id though.
-
It's working for me on several Jira instances, so yes, it's perfectly possible and you probably have not set it up correctly. However, "it should show to reporter or commenter as "Awaiting Response".... regardless of the workflow status." is nonesense. If "Awaiting response" is a status, then you need to move into that…
-
Yes, that's exactly what the auto-transition listener was written for. See https://ecosystem.atlassian.net/wiki/display/JTOOL/Auto+Transition+Listener
-
>When issue is created with issue type Story , i cannot change the sates of workflow Do you have "transition issue" permission in the project? If you do, then you'll need to look at the workflow itself to check the conditions on the transitions to see the rules that are blocking you from using them. >There are no Issue…
-
I ran into this one in a 3.5 install - you do need to tell the database to default to using InnoDB, at least during installation of Confluence, because the setup will simply use the defaults the database is set to. (Ubuntu is based on Debian, so there's a strong chance it will be the same for your Debian box)
-
That "original" problem is still correctly answered. Labels are designed to allow users to add items. If you want to limit them, use the multi-select. The secondary problem of the multi-select feeling uncomfortable - totally agree. Atlassian are moving that way though - have a look at the components field. There's an…
-
I think you need to look at the dates - the answer was valid four years ago in JIRA 4. The interface you're talking about is a later and better one, for both types of field. Also, the question was not about the interface, it was about how to handle the content.
-
Um, that kind of renders labels pointless. Multi select fields are there to allow people to put tags on, from a pre-defined list. Labels are there to allow the user to tag things with whatever they feel. There's nothing in-between those - either you want a pre-defined list (use a multi-select), or you want the users to…
-
For the first half of your question, lmgtfy - http://confluence.atlassian.com/display/JIRA/JIRA+as+a+Support+System The second half, about the reporters permissions, is not mentioned on those pages, but it's here at http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission
-
The sizing guide for JIRA is fine for this - just think of your Agents as normal users for this purpose - https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html
-
I've not seen one - our users simply use Confluence. Be warned though - Confluence 4 is binning wiki markup (with some back-porting stuff to enable you to type it and have it automatically formatted to the new structure, and macros to display it if you must keep older stuff in markup)
-
They've changed their settings in excel. The raw data in the xml Jira generates has not changed - you can check what it is by opening the downloaded file in a plain text editor - vi/nano/gedit/notepad(ugh) etc. You should find that the date is coming out in a date format, and all your users have done is chosen to use a…
-
Yup, you can only search for issues. Projects are not issues. But that's the sort of query that gets you started on your housekeeping!
-
Sadly, you're spot on, there's no easy way to do this, you have to check each project separately. I wrote a housekeeping report which helps with it because it exposes most of the helpful information in one page, but it's still missing a couple of fields (the most important ones) and I've never got round to upgrading it…
-
It should be possible, but a lot depends on what you mean by "integrate"?
-
If it's new, then there's no old number for it to change to a new one from. But the transition from "new" to "triaged and decided on" won't change the number unless your process involves moving it to another project.
-
Depends on how you transition it. If it stays in the current project, the number stays the same. If you move it to another project, it will get a new number.
-
Help (? at the top right) -> about JIRA
-
That simply means Tomcat couldn't get Jira to start. You need to read the application log to find out why. Should be atlassian-jira.log, but you can also look at catalina.out in the tomcat log directory too (it's often longer and hence more painful to understand, but can tell you more)
-
I know, but how are you going to handle all the people asking why they can't rank them or get rid of the unneccesary clutter they cause?
-
Because it's extra code for no benefit, all that happens is you get people asking why they can't rank the subtasks, and complaints that there's too much on-screen that doesn't do anything.
-
Ah, now that's related to a different problem. JIRA Software essentially does not support estimating at sub-task levels. Move the estimates up and it'll work quite well. "Moving the story around does not update the Kanban board" suggests that your boards are configured in a way that means some updates don't appear. We'd…
-
So demonstrate some. My imagination may well be limited and I simply can't work out any real use for it, and that's why I say what I do. If someone could show me a useful case, I'd accept it. No-one has yet - they're usually not understanding the backlog evaluation process.
-
I understand that it's an opinion, but I still cannot see any value in seeing the subtasks. If you would explain how they are useful to you, I might, but until I see that, I can only assume that you're doing your estimation/ranking at the wrong levels.
-
You don't really explain why your subtasks are apparently so important. To reuse your analogy, I'm not saying "there's no need for you to have orange juice", I'm saying that when you are looking at a backlog, and you decide you want some orange juice, you are then trying to rank that as more or less important than desires…
-
I don't think a backlog view of a story is the right place to be re-estimating stories. The backlog view is for prioritisation and planning a sprint. If a story is the wrong size, then you'd normally go into it so you can re-size it based on all the information on it. A summary, even with a pile of sub-tasks, doesn't…