Comments
-
What does the marketplace say the price is? (From memory, it says free)
-
Make it optional in the field config and, if it is the resolution field, remove it from the Create and Edit screens.
-
You should not need a post function. Just remove resolution from the screen - that's what the problem is - the users are setting it simply by going through a screen with it on. You do need to think about this field - even if you don't have it on any screens, it's worth blanking and setting in your workflow so you can…
-
Ah, hang on, I have not been clear. I apologise. This is a quirk in Jira I keep forgetting about. None very much is an option for this field. However, the field assumes that if you put it on-screen, you are wanting to set it, so it does not offer you "none". You need to make sure the field only appears on transitions that…
-
I already answered that. NONE of them. The field needs to be empty.
-
Yes, the "specific value" is "anything", as opposed to "nothing" This field is used by Greenhopper/Agile, but it is part of the core of Jira. Whether you think you need it, or even use it, you need to be aware of it. The whole of Jira works off a simple idea - if the resolution is set to anything on the resolution list,…
-
Status is NOT resolution. Look at the resolution field. The strike through is controlled by the resolution.
-
It's much the same as above, you've set up the workflow to set a resolution as the issue is created. Check that the "create" screen does NOT have a resolution field, and that there are no workflow post-functions that set the resolution.
-
The list of resoltions is more of a sanity check than anything. Some people don't grasp that "unresolved" is a spectacularly bad option to add to the list, and do it without engaging their brain and then wonder why it looks odd. I just wanted to rule that out as a possible problem. Your screenshots pretty much said it…
-
Hmm. That's looking right, barring the activity stream. Could you check your list of resolutions under Admin -> Resolution. Make sure that there's definitely NOT one on the list for "unresolved"? If there is not, then I'd raise this with Atlassian OnDemand support, as it looks wrong to me.
-
I think your karma mght be too low to allow screenshots. Can you tell us what colour the issue's resolution is in the issue navigator? Also, what version of Jira are you on, and do the strike-throughs appear when viewing the issues in their main view screen?
-
Ok, pick one of the newly created issues and look at the issue in Jira - what does the "resolution" field say? Also, can you do a search and view it in the issue navigator? Make sure the "resolution" field is in the result as a column - what does that say (I'm fishing for the colour of whatever it says as well as the text…
-
You've set something up that sets them as "resolved" as they are created. Or your users are *really* quick at resolving them ;-)
-
All sorts of things can do this. Start by reading the log file from when indexing started, see if there are errors in there.
-
I think you need to ask a question before we can help you.
-
Here, as it's going to replace the forum sometime...
-
Mmm, I knew they were waving people this way for general help and advice from the beginning of OnDemand, but I don't think that's very fair unless they're going to plaster a "this is not official support, it's the community" type warning on the link. I'd be tempted to raise the support request, and mention that they're not…
-
Er, Answers is for the community of users of Atlassian products. Of course, that includes Atlassian, and they are here, but under no obligation to say anything at all. If you want them to answer, raise a support call with them
-
My reading was slightly different - I thought the trick might be to have everything you've just said, but instead of the testers entering the resolution, you might copy it from what the developer said earlier, on a "pass test" transition. Obviously, needs a spot of code to copy from custom field to resolution.
-
I'm not sure what you're looking for here. The application does things like "if you delete an issue, remove all the custom field, comments and history data for the issue". I think it might be useful to know why you're asking about referential integrity?
-
You don't really need it - the application handles it all internally. Adding referential integrity checks into the database would be pointless and could cause problems with the application.
-
It's quite simple - if you don't have JIRA Core, you don't have issue types, workflows, screens and so-on. Because you don't have JIRA at all. Core is just plain JIRA with no applications like Service Desk or Software.
-
I converted this to an answer because it could well be the right one. It was next on my list to ask
-
Are any of the 179 sub-tasks? Which won't appear in planning because they're useless there?
-
That setup works fine on all the Jira systems I've used recently, as I said on your original question about this. You'll need to start full debugging - look at logging outgoing mail to see what it's trying to send. One other nagging doubt as well - your email handler might be binning the emails, have you got "notify users"…
-
If you include "reporter" in the notification scheme on the "issue created" line, then Jira sends the reporter an email when they create the issue (including the issue ID and some detail). It removes the reporter from the list of recipients if they have the "do not email me on changes I have just made" flag set on their…
-
Why have you said "without adding eg dynamic plugins forms"? You need code to do this, plugins are your best option. (Probably the behaviours part of the Script Runner for JIRA addon)
-
You'll need addons to do that reliably. Why are you ruling that out?
-
You may want to give us a bit more to work with.
-
You have a field called "application". You have set it as mandatory in the field configuration, or, possibly, added a validator to the "create" workflow action. So, your users need to fill it in when creating the issue, and my guess is that you have not included it on the "create" screen so that they can do so. Either…