Comments
-
Not natively. You can search for a sub-string (although the search is fuzzy), but not do a bulk-edit to change it. I'd 'cheat' and write something in Script Runner to do the search and replace as a one-off.
-
We don't need your support details - we're not support. You should have the field "original estimate" available, assuming you have enabled time-tracking and have not messed around with your screens too much. See https://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking
-
Yes, that makes perfect sense now, thank you! Makes my answer mostly irrelevant too, but we can try. The "name" mention in the error message suggests that it's picking up a property name instead of a value there. Could you show us how you have configured the connection?
-
I'm not sure why you're trying to use Confluence's database for Crowd. The two systems should use separate databases. (They can be on the same server and use the same user to connect, but the databases need to be separate)
-
Not without hacking the core code. The subtask types can be displayed, but it won't group or order by them without some tweaks to the display code.
-
1) You can't have a sub-task that isn't a sub-task. Child tasks, sub-tasks, sub issues, doesn't matter what you call them, either you have sub-tasks or you don't. You need to decide whether you want this pre-production stuff to be a sub-task or not. 2) Depends on your decision in 1. If they're sub-tasks, they're linked by…
-
To echo Renjith, it's not the sequence. It could well be load, but you also need to make sure that you are not running interfering virus scans (assuming you're on windows), and you have the right version of Java - only the latest versions of Jira run with JDK 1.7 and this startup problem can happen if you run an older…
-
Could you check the "conditions" on the workflow *very* carefully - paste their definitions here so we can see them.
-
Check the permission scheme and workflow - do you match the conditions for using the transitions? If it's the default workflow, then you need to be in the role of user or developer to get the permission "can tranistion issue". (Just because you're an admin doesn't mean you can do anything - that's a dreadful permissions…
-
A partial help - use "bulk edit" to make changes - while selecting what to change, you'll be offered "do not send email for these updates".
-
No. A sub-task is an issue in a project. It takes the project key just like all the other issues in the project.
-
The url for the icon is not responding when JIRA tries to use it. Go to Admin -> Issue Types and change the url for the icon to a valid one that JIRA can read, or upload a valid icon
-
Sounds like the right procedure (although moving from Linux to Windows is generally a downgrade, it shouldn't affect files like this) I'm afraid your best option remains comparing a healthy install with the old one to check what else might be missing
-
If you're missing these icons, there's a strong warning that you could be missing other stuff. There's no way of knowing what unless you can compare this installation with an undamaged one. Putting the icons back by copying them from the Linux box will fix them. But not anything else you might have lost. How did you…
-
Could you tell us what authentication you are using in Jira? Is it the internal crowd, or something else? Whatever it is, you will have to import your users from your old table (including processing passwords, because it's really bad design to store an actual password and Jira/Crowd do it properly and hash them)
-
Yes, click "attach" You may need to increase the attachment size limit in Admin -> Attachments though - the default is 10Mb
-
Divorcing "can log in" from "has access to almost everything" default usage of jira-users is the first thing I do to JIRA systems. For the last 12 years!
-
>Give that group permission to login in the Global Permissions Remember that this means all new users will be added to the client group.
-
I'm pretty sure there's a handful of user renderers in later versions of Jira, and you can add your own. If the information you want to display is already in Jira somewhere, then writing one of those would probably solve the problem. Although you may want to override one of the built-in ones rather than add a new one. I…
-
Gottit - https://developer.atlassian.com/display/JIRADEV/User+Format+Plugin+Module Unfortunately, that seems to be for V4. I don't know if it works in V5 (I was only looking to use a nicer format that the one I'd whacked into a plugin because I didn't know any better)
-
It's not implemented in OSQA the way you have described. There's a field on the profile that you can fill in and it gets appended. You can put anything you want in there, it's nothing to do with your email address, website or anything else. Try whacking a random string in there. As an example, I can set mine to Kitteh, my…
-
Generally, you can't. Only admins can get the details of workflows. You can get a basic view (the flowchart, but not conditions, properties, screens etc) by hitting "view workflow" on any given issue though. It appears under the issue status - as long as you have "view workflow" permission (and you're on a relatively…
-
As well as Phil's point, make sure the user has "transition issue" permission in the scheme (it's a general permission that protects all transitions without appearing in the workflow. It stops "anonymous" users from being able to use transitions!)
-
Not really, but talk to sales-at-atlassian-dot-com to see if they'll vary the standard patterns
-
Ok, all of those fields, except "labels", are system fields. * They're built into JIRA.* You can NOT change the "context" of them - they always exist for all issues, even if they're not used. * You CAN remove them from screens, so people can't edit or add them, but they will still display on the issue view if they have…
-
I'm afraid this sounds quite complicated. JIRA is this way for historical reasons, but it does give us quite a lot of flexibility too. Atlassian want to simplify it as much as we do, but I don't know how far through they are. Anyway. You have a list of fields. There are three things to look at: * Field Context - this only…
-
Both. Have stories (and others) inside Epics, and then when a story needs splitting up for allocation to many people, or just because the developer wants to break it down a bit, use sub-tasks.
-
No, you need to merge the two queries together. Project in (TT, TO) and issuetype = "Bug"
-
You can only do it in very recent versions of JIRA Software. See https://confluence.atlassian.com/jirasoftwarecloud/reopening-a-sprint-785332001.html
-
Yes, the two fields are separate (assuming they're standard fields). If you remove an option from the first one, it won't affect the second list at all.