Comments
-
Have you made sure the "set resolution" function uses *exactly* the same string as you've got for the N/A option?
-
It's not an arbitrarily imposed limitation, it's done by design. An arguable one that I'd be strongly tempted to change to a completely different model of course. But it's still not wrong, your workflow doesn't take account of the way things are, so it's incorrect (until the rules are changed).
-
Um, yes, your workflow is incorrect, so you need to edit it... Note, there is a known bug in Greenhopper in that when you convert projects to using the "simplified workflow", it puts "clear resolution" on ALL the transitions. See…
-
Ramiro, that does not work. If you add the resolution to a screen, Jira removes the none option from it. In other words, putting a resolution on a screen sets it, even if you want to unset it.
-
The "reopen" transition should have had a "post function" on it that says "Resolution will be cleared". I'd re-add that transition and then cycle back through closed and reopen again. (You can't just put resolution on an edit screen - Jira removes the "none" option from it)
-
No. A sub task can only have one parent, by definition.You can use issue links to connect issues when the relationship is not parent/child
-
No. A sub task can only have one parent, by definition.You can use issue links to connect issues when the relationship is not parent/child
-
Ok, I think you've misunderstood what the boards are slightly. Boards do not contain issues like projects do, there's no "delete task from Kanban board" or "add task to Scrum board". Boards are best thought of as a view on to a set of issues. If you change the status of an issue (or fields, or anything else), that will be…
-
I'm afraid this question doesn't mean a lot. While the basic idea of "I want to show the user some information when..." makes sense, the rest of the question has no context. Click to update something is a common idea, but, in JIRA - click what? When? Why? What, in real JIRA terms, should happen?
-
Not quite. They added "resolution" to some of your Screens. The field exists on all your issues (and hence projects) automatically. It's always there.
-
>The field is always mandatory I'm afraid that is incorrect. The resolution field is NOT mandatory in JIRA terms. It is optional. It must be optional, because the users need to leave it empty until such a time as an issue is resolved. The definition of a mandatory field is "it must have data in it". So, the field is…
-
The resolution field is not technically mandatory, but it does not have an "empty" value to select, so it always gets set if it is placed on a create or edit screen. You must not put the resolution field on any create or edit field - only view or transitions into "end" type status.
-
My apologies, as I posted that last answer, the way comments cross over makes it look like you had posted "do you have the power to amend answers" then changed it to "do you have the power to delete". Now I come back to it, it's clear. I am sorry I misunderstood that.I don't see that "try our sso" is any different to "use…
-
Ah, you edited your comment and made my comment less clear.You originally asked if I could "edit" answers.I don't know if I can delete them - I don't think so, but I wouldn't do it even if I could. I can delete users, which then deletes all their questions and answers, but that's only for killing off spammers in my…
-
There are many products for SSO out there, as well as trying to do it yourself. Make sure you consider the pros and cons of ALL of them, not just the one you've seen the first advert for.
-
Yes, but I don't touch them unless they are blatantly wrong and potentially dangerous.The problem (in my opinion) here is that your answer is an advert for your product. I'm not saying that your SSO is the wrong solution, just that it should be looked at alongside the other SSO products. It is not the only one, and another…
-
To my mind, it's not an answer. The answer is not "use my product", it is "look at all the products and select one". I guess that's why someone is changing them to comments.I think it's worth restating that there are many SSO products out there and the questioner should really look at all the offerings.
-
I've seen the DIY solution on Kerberos work perfectly well in a couple of places. So please make sure you look at all the options.
-
Please be aware that there are MANY options for SSO in Jira and Confluence, and you should not be swayed by one advert - please consider all of them.For the record, I work for another one of the vendors of an SSO system for Atlassian products, but I have not actually worked with it myself. Before I joined them I worked…
-
You probably want to look through https://confluence.atlassian.com/display/DEV/Single+Sign-on+Integration+with+JIRA+and+Confluence
-
Yes. If you delete issues, or even whole projects, before you export from your current Cloud systems, it won't delete any schemes or other configuration. Although I would recommend a quick look through the stuff that could be deleted - always worth housekeeping.
-
Yes, a backup contains all of your data and can be imported on your new Cloud system replicating everything as it was in the old one.
-
That suggests a broken index then. Could you try re-indexing the project?
-
Could you pick one of the stories that the filter is excluding and check its project, status and issuetype are definite matches?
-
There is no search inside a search. Quick search is just an entry point into search.The context of the current search is that it is a search - there's nothing in it for JIRA to read your mind on how many results you might want - how do you expect it to know that you want 10 per page from "project = X" and 50 a page from…
-
Number of results returned in a query is more likely to be a human thing. The two people I currently work with most closely have completely different approaches to the way they work and if I inflicted an arbitrary number on either of them, it wouldn't work for the other one. Steve likes a simple "top 10", Dave wants "as…
-
It's the other way around. Every user can set the number as I already said.What you've found is the default setting for those who do not adjust their profile.
-
It's a setting in each person's profile - "page size" last time I looked
-
and it's incredibly frustrating to have a question where you haven't bothered to give us even the most basic information on what investigations you had done. My cause and fix was totally different from Jo-Anne's and wouldn't have helped you. But there was no way of knowing that, so there was no point in volunteering it.…
-
Is it consistent for all users, or just some? Or is it consistent per project? Does it goe away if you refresh? Is there anything in the logs? I'm guessing in the dark here - you've not told us anything that suggests a pattern. Yes, I have seen Jira do this, but I know why...