Comments
-
That's not something Jira supports. Defaults for custom fields are set by field contexts and are hence the same for every user. System fields mostly don't have defaults, but when they do, the normal behaviour there is to use the last value you used, not any particular default I think the behaviours plugin would let you do…
-
Yes, that's fine, but setting a resolution of blocked does not make sense. Blocked implies that the issue will be picked up again and worked on. So it's not resolved, it's just not moving.
-
Does "blocked" mean "we will not do this issue" or "we have dealt with this"? If it does not mean that, then it should be unresolved. Blocked is usually part of a workflow, so it's a status, rather than a resolution.
-
Correct. JIRA uses the resolution as a broad "this issue has been dealt with" flag. So you really only want to set it on issues that you're not going to need to do any more work on.
-
>For Example the status Work In progress, the resolution should still be in progress if i click on a transition that leads into this status. No, that is wrong. The resolution should be empty when the issue is in progress (this will be displayed as unresolved ). You should, in almost all cases, only set the resolution when…
-
Ah, comments crossed over. You've spotted what I was explaining.
-
It's explained above, but let's try it again. You're ignoring the third answer to the question of "not answered". Is <not answered> in (a, b, c)? You can't tell because you don't have an answer. You need to explicitly catch "empty", because it's not the same as "look for empty in a fixed list"
-
It's at least half my fault for not reading your question properly. Probably all my fault. My explanation stands, but only gets you halfway there. The query certainly only gets you half an answer. Try: Project = MyProject and type in (Epic) AND (component is empty OR component not in (MyComponent) )
-
Ah, yes, human language lets us down a little here. "component not in <complete list>" is logically not the same as "no component". The way we think in a more fuzzy logic than computers falsely equates the two ideas. The first one is implying that you're looking for a specific component, so an issue has to have one for the…
-
Hmm. >As I understand an email notification using notification scheme works on a project level and not by workflow level as what I wanted No, that's not the right way to think of it. There is no "workflow level". A notification scheme works on events. It tells JIRA to send email to a selection of people when a certain…
-
Not the way you describe it - the workflows have nothing to say about non-workflow activity. If you use the "assign" link on an issue view, you'll get an "issue assigned" event you can use in the notification scheme. "Issue updated" goes out on an "edit" such as just changing the assignee without using the assign link. All…
-
Nope, if you can see the project, then you can see the things that belong to that project. There's no way to hide components from certain users because it doesn't really make any sense to do so. If there are genuinely things to hide from them, then you should probably be setting up a separate project for them.
-
I'm sorry I cannot answer you in Spanish, I'm afraid my language skills are dreadful. The error message is telling you what is wrong, and your database information confirms it - you have not created a database for JIRA to use within your postgres system. JIRA will handle all the table creation and initial data during the…
-
Sorry I couldn't get to this sooner! I was going to follow up with a quick run at "create a new screen and associate it with a transition" and going step by step, but you got there without me :-)
-
No, you definitely don't want the resolution screen to be used in edit, that can break your data quite horribly. I'm not sure what is wrong though. During a transition, you can tell Jira to use a screen. You should simply take your resolution screen and associate it with all the "resolve" or "close" transitions. I'm…
-
What type of query? Plugin? Database?
-
Oops, I missed the onDemand flag again. You can't add plugins to OnDemand, so you're stuck with it I'm afraid.
-
Heh. Category is a really simple flag on a project, and, as you've discovered, pretty much neglected everywhere. Version 4 of Jira at least allowed you to search on it (unlike 3.x), but even 5.x hasn't improved the output. My answer for Jira 3.6 was to code a really simple derived field that drew it out into the navigator…
-
It's just a list of things that might be wrong that we've seen a few times before here - let us all know if it's none of them!
-
I suspect an inexperienced administrator has done one or both of these things: 1. Put the resolution field on the Create screen (This breaks it because when the field is offered to the user, it ALWAYS sets the resolution to something. You can't blank it out) 2. Added a resolution called "unresolved". Which breaks Jira…
-
You can't back up a project, only the whole system. Please see the documentation I linked to on backups.
-
See https://confluence.atlassian.com/cloud/data-storage-faq-744721620.html and https://confluence.atlassian.com/display/JIRAKB/How+to+Automate+Backups+for+JIRA+Cloud+applications
-
Your permission scheme probably says "Browse = Role: Users". As you've removed jira-users (which usually includes everyone who is able to log in), you've removed all visibilty of the project from people. You'll need to think about how to let them back in - adding them individually, putting other groups in the role etc.
-
It's for users to log their actual efforts (as in a length of time spent) on the issue. You can then report on that to see what issues are chewing up your resources, how long things are taking to do, and generate/work with estimates based on time worked. Might not be of any use to you in an Agile context.
-
Draft mode in the editor only allows certain actions. Changing the create transition's end point is not one of them, so you need to copy the workflow and edit the new one, then migrate to it.
-
Admin -> custom fields Use the admin search if you're not sure
-
Try going into the list of custom fields and deleting them completely. If they're not there, then you've got a problem - the best and most safe way to do it is to install the plugins that provide the fields you don't want - that will let you go into the custom field admin and delete the fields cleanly.
-
You haven't set the reporter to get "issue created"
-
This is not how a forum works. You ask questions to be discussed in public, not for us to contact you privately. Anyway. Yes, what you need to do is set up a connection to your inbox, then a "handler" to tell JIRA what to do with incoming email. Then you configure the target project to send a "notification" out to the…
-
There isn't a way to do this really. It's more a case of trusting the people who have the rights to add to a sprint.