Comments
-
Quick filters are not related to swimlanes, they do two different things.
-
Go into the swimlane definition and add a definition of "filter", You get to name the filter (that appears on the left) and give it some JQL (so, "priority = x"). Repeat for each priority and you have it. I think that's maybe what Jose was getting at too, although he's used the wrong language - a quick-filter is a filter…
-
You can't. If I log in as abc, then I'm abc. You have no way of knowing who that is. You need to give them separate accounts. That's the whole point of user names!
-
Not really. Top level and sub-task issue types are separate - a top level item cannot be a sub-task of something else, and a sub-task must have a parent. There's nothing to stop you adding a sub-task issue type of "bug" though. You won't be able to use the exact same name (That's from memory, that may have changed) and…
-
There is no downgrade process. You could try exporting the xml, hack the version number and try importing it into a 6.2, but it's unlikely to work without some hacking of the actual data as well. There's actually a very good chance that getting your users to upgrade IE to a supportable version (or better, use a proper…
-
Er, we're not talking about custom fields, it's validators that matter here.
-
Mmm, I think they misunderstood your question, and then went on to pick the wrong addon!I read your question as "when the user clicks on the due date, I want to limit their options to today and onward, so they can't select dates in the past". That's something you'd need to implement actually in the date picker and field,…
-
The Toolkit doesn't do fields like that. What function are you actually looking for here? (As I don't understand why you've gone for the toolkit)
-
Yes. (That's a really easy answer, but there's not a lot more to say. The addons co-exist fine, although you might have some issues with your desired processes if you try to do Agile on Service Desk projects. Nothing insurmountable, but it can be a little confusing sometimes)
-
Do you have the "browse users" global permission?
-
Oh, well spotted, I keep forgetting you can do that!
-
The search is remembered by user account, it's a convenience for them. However, the jump from "homepage" to "search" is not being done by Jira - you've added javascript or html that redirects them. You'll need to remove that.
-
No, you can't change it, you'll need to ask for a new one and migrate your data over.
-
This means one of two things: * The transitions do not exist in the workflow for this issue in this project * The user does not have permission to execute the transitions
-
I tend towards the first option myself, because it makes more sense (to me, I should point out. I'm not a service desk manager, so I'm not highly qualified to comment). Projects and Service Desks will tend to be organised along team lines, and will normally be supporting many different users, who will have different…
-
I've seen it done several ways. Broadly though, there's two basic approaches * Set up the SLAs to include an indication of the service level any issue was on (there was some scripting to set it from the customer's details) * Have different projects and service desks for each level
-
You'd change the workflow to make it go through a transition that uses the resolution screen.
-
This space is based on OSQA, not Confluence, but a lot of the lessons Atlassian have learned developing this site have gone into "Questions for confluence" - have a look at https://www.atlassian.com/software/confluence-questions
-
If it's enabled (i.e. paid for) in your OnDemand account but you're not seeing it, contact OnDemand support.
-
Not really, I don't know your data, so there's not a lot I can tell you.
-
For each custom-version, you'll need to run a filter to find out where it's in use, and then use "bulk edit" to add it to the actual version field. You might be able do something with jelly or scripting, but the first step is to analyse the volume and complexity of the data to see what route is best.
-
Hmm, in that case, he's describing something Jira does not do. You can't change an issue type between parent and child. The closest I can think of is that you rename <sub task> to "fred", then rename a <top level type> to <what the sub task was> then rename <sub task fred> to <what the top level type was called before>
-
$recipient.getEmail() should return a string, from memory. That means you should be able to use $recipient.getEmail().toLowerCase().contains("ext") Bear in mind that you probably need to be a bit more clever than that though - what happens if you work with users who have emails like Dave.Nexte@yourplace.com ? (I'd reach…
-
Yes, that's what we said. That's where the help goes for most fields. You need code to do it differently - a new way to draw up the fields and some way to enter and store the text you want.
-
Most fields don't support the ? - that's for the more complex help people may need with system fields that do clever things. You need to put your help in the simple description field as Vasiliy says.
-
I'm afraid your question is a bit unclear, when it is read in a JIRA context. The quick answer is "yes", because the way JIRA works is to hang a lot of the configuration off the issue type. So that within one project, your issue type can determine the fields, screens, and workflows differently for each issue type. The…
-
Yes, include them in the notifications. In the notification scheme, select what event(s) you'd like them to be notified about, then look at the bottom of the "possible recipients" list. The top part of the list has the obvious ones like reporter, assignee, group, role, etc, but near the bottom, there's one called "user…
-
What are the conditions on the workflow, and probably more importantly, is the user actually logged in when they can see the issue but do nothing with it?
-
I'm not entirely sure - the code for the messages Atlassian generate is in the surrounding structure, but I don't know if they are feeding the message out of the java.
-
I'm not sure that this is possible inside a workflow function - the landing point at the end of a workflow is determined by code around the outside and I don't think you can simply subvert it in a post-function. I think the landing point decision is made in the urls and .jsps that handle issue actions, so you'll need to…