Comments
-
I'd also look at https://confluence.atlassian.com/display/AGILE/Working+with+Epics for a description of Epics - they are VERY different from components.
-
Look at the permission scheme for the project, cross check the browse settings against their account
-
They probably don't have the rights to see the project. Skip the agile stuff for now and check their Jira permissions.
-
Ah, that's one of the few features that Atlassian removed! The only way to do it now is directly hack the templates in the code that draw that area on screen. See (and follow, and vote for) https://jira.atlassian.com/browse/JRA-25151
-
That's not a custom field of type original estimate. That is a field of type search for original estimate. Note the search. It adds functions to let you search the system field, and edit it in-line. It's not a data field. So while you might put it on a screen, there's nothing to display in view or edit mode, so nothing…
-
You can't add fields of type "original estimate", so I'm not sure what you've done there. But the thing I suspect a generalised point, not field type dependent. Is there any data in the fields? If not, then they won't display on issue view.
-
I'm sorry, I don't understand that. Who, exactly, should be made the assignee?
-
Assignees are always individual users. Do you mean you want to set it to a member of a particular team?
-
Follow the documentation probably.
-
Again, you should really try a quick search in the standard documentation before asking here. For this case see http://confluence.atlassian.com/display/JIRA/Configuring+Workflow Look at the "transitions" on the steps. They have three tabs - Conditions, Validators and Post-functions. Conditions are what you need to add…
-
There is a far easier solution than security levels. With security levels, it's actually quite hard to get it right and most people don't. See https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission for the better solution.
-
I stay away from fiddling with javascript, and I'm not really sure where the js validators for date fields might be found. You will be into However, I would start with a look at debugging the moving of issue type - that doesn't involve javascript at all so you may have another problem which "fixing" the date check isn't…
-
Indeed, although it's the code for the field type, not the individual field.
-
Um, well, that's actually still a valid year. I don't think there's a simple fix for this - the checking code would need to be amended.
-
Again, it's coded to respond to an "order by" clause.
-
I think it's the same answer as above - the issue navigator is coded to look for "order by" or whatever the standard sort order is. Your function is giving it a list of issues to work with, but not the order, because you've done it inside the list, and not with an "order by" clause it can read.
-
You're mixing up "sort" with "order". Java lists have an order, but that order is arbitrary and internal. They are NOT sorted. The very fact you have to move to an ArrayList to do any useful sorting is a bit of a giveaway here. What I'm trying to get across is that the order the user types stuff in is not relevant to the…
-
You've missed my point. The list returned by JQL does not have an order. You haven't said "order by", so you just get the unsorted list. It's irrelevant what the user typed in, JQL has no results order unless you add an order by clause (and that only kicks in when you're using something that uses it). What you need to do…
-
I'm a bit confused here. If you run JQL with "order by", it comes into the navigator. If you run it without, it uses the default. But what you're asking for is "the same order that the JQL returns it". But unless you put in an order by clause, JQL doesn't actually have an order, it's a list of issues. So what you're asking…
-
You aren't telling us anything!
-
Make sure you have the "component/s" field on the issue creation screen, and you'll be able to select them as you create the issue. Have a look at the project's "issue type screen scheme" to drill down into the exact place you need, or, as an admin, start creating an issue and use the "where's my field" helper.
-
Errors from add-ons usually get echoed out to the application logs, so I'd start with a look in <JIRA home>/logs - probably atlassian-jira.log first
-
I can confirm what Justin says here - if you buy a licence for JIRA Software, it'll work for licencing JIRA Agile in older servers as well. You will probably want to look at upgrading your JIRA soon too - 6.4 is the lowest supported version.
-
Ok, 1 and 2 good to know, thanks 3 - is that a parent issue type or a sub-task? 4 - Ok, so he was looking at the board, but how exactly did he delete it from the sprint? 5 - Interesting. The issue details are all correct though? It looks fine until they click "show on Agile board"?
-
That was a little bit of a short answer on my part, sorry. Some questions though * What *type* of Agile board are you using? * Assuming it's a Scrum board, have you checked the entire backlog for it? * What type of issue is it? * How did the issue get delete from the sprint? * What happens if you go to the issue in plain…
-
That you've removed it from the sprint.
-
Make sure ALL of your permission schemes limit the right to "create issue" to people who have accounts (specifically, check for "group = anyone" and remove it). You can find out which schemes are allowing it by logging out and clicking create, picking a project, logging back in and looking at the scheme for that project.…
-
Create a new user, make sure it has full read/write access to the installation, then set the service to run as that user.
-
I'm afraid your question is too vague to answer. You can change a user to another by logging in as the other user or using a "work as other user" function. But I suspect your question is about application ownership, logging and so-on, but I'm not sure where.
-
That is very odd - none of the Confluence systems I've got access to are running anything like that (or, if they are, it's infrequent and I'm simply not getting it in the logs) You probably need to examine the add-ons you're using to see if one of them is causing it