Comments
-
No, I'm sorry, I did not phrase that correctly. I wanted you to check the permissions on the top level issue. Look at one which has open sub-tasks and check that they are NOT offered "close" as a transition. Then look at another that has all it's subtasks closed - can they transition it manually?
-
Hmm, well, it all looks to be set up correctly, so the next question is if your user executing the sub-task change also *could* close the parent if they look at it in standard Jira view?
-
Ah, actually, I've just realised it isn't. Agile adds a function that does the automatic close, so I suspect yours is not working at all!The workflow you've given in the screenshot looks fine, but can I just ask if it is the only workflow for the project? If it is not, then what issue types is it used for?
-
Resolution is not required on the transition - only the validators do that and you've said you have none.You could have a point though - could you try adding a post-function to the *parent* workflow of "set resolution to fixed" (temporary, of course) and see if it works then?Also, does the person closing the sub-task have…
-
Do you have any conditions or validators on the "close" transition?
-
No, I think you'll need to raise this with Atlassian support. Before you do it though, I'd double check that the workflow scheme for the project and the field configurations. The workflow has to be the same for the issue types, and the field configurations have to be "compatible" (or, ideally, the same config for each…
-
Sorry, I've misled you. I was looking at version 4.x, not 5. 5 DOES implement a lot of the "move supermarket around" stuff, but not all of it. It can cope with you choosing a different issue type, as long as the issue type is SIMILAR to the one you initially selected. If it's too different, then it won't let you select it.…
-
It shouldn't be showing you any issue type box on create at all, that doesn't sound right (also, it's not a "combo box", it's a select list, so if you've got a combo-box, I'm misunderstanding something) It should be easy to fix though - go to the "screen" you're using for "create issue" and remove "issue type"
-
It's a nice theory, but you do understand that the coding would be a nightmare? Every time a user changes and issue type on the create screen, you'd have to go back and re-build the entire screen, working out every field setup again. That's a lot of work for both developers and the browser, it's far more efficent to prompt…
-
It's not a bug, it's the way it's designed. You shouldn't be able to change issue type on Create - the whole point of the prompts you see before the main screen are for your users to select the right project and issue type. The reason is simple - ALL the configuration is hung off the issue type. Jira has to know what issue…
-
You need to remove them from the group(s) that can create personal spaces. Check global permissions to see the groups you need to examine.
-
No, the whole point of Jira is that it tracks issues. The screens are a niterface on to the issues. It's nonsense to have a screen that doesn't interact with an issue - where does the data the user enters actually go if there's nothing to put it on? It's not a "limitation", it's a "thing that has to happen"
-
I'd avoid it too. Especially with MS-SQL as it's so flaky. If possible, run two entirely separate databases so you can follow the recommended collation settings for both applications independently.
-
Yes, you need to have the correct database collation settings. I thought all the database servers supported having different collation settings on different databases though. So you can have "mydatabaseserver" running and hosting jiradb with one setting and fecrudb with another.
-
Look first at the licence for JIRA Core/Software/Service Desk - what do the licences for them have? You need to replace these with developer licences. If you have Software or Service Desk, do them first (you might find it easier to disable them first - then they won't check for licences and you can replace the Core licence)
-
If you're using plain JIRA issues to handle test sessions, then look for the "attachment" options under the issue, or drag them into the comments while editing. If you're using some add-on designed for testing, then you'll need to read the docs for that, as we can't help you without knowing what it is.
-
You don't - the accounts are totally separate. You'll be able to log into both of them at the same time, in separate browser tabs, but the two systems are totally independent of each other, and are unaware of the other's user base. Your external company can add you with the same credentials as your other account, but it's…
-
Delete the custom fields, then remove the .jar files. If you need to retain the data in them, then your job becomes a lot more complex. I'd actually cheat and either hack the database to swap them to another custom field type (very risky, not for the faint-hearted or inexperienced) or write read-only fields with the same…
-
You need to remove the resolution field from the edit screen. It should only be placed on transition screens which are moving the issue into a "closed" or "done" type status. Yes, this loses the ability to set it on an edit action, but that's easy to fix - you place looped transitions on the closed type status (i.e. closed…
-
I'm on a smaller laptop and don't have the problem. What about the other questions you were asked?
-
DoD ? Dungeons of Doom? I'm not seeing that problem, unless I do something silly like shrink the browser to an unusable size. Could you explain when it happens and what version of Agile/Software and JIRA you are using, along with which browser you are on?
-
Please, don't duplicate questions. You've asked this separately as a full question already
-
Remove the nulls from the incoming data. A simple empty field will import no data fine.
-
You can't. JQL searches for issues based on fields, not permissions. The only permissions that matter is "if I can't see the issue, don't include it in the results". There might be a couple of JQL functions in addons on the marketplace that do this, but I've not stumbled across any.
-
Check your rights include Edit - an admin gets rights over settings, not necessarily any content (I'm an admin here, 780 spaces, I can only edit 12. I can give myself the permission to edit the others if I feel like it, because I'm admin, of course) Secondly, check the plugins - are there any disabled that are in the…
-
I've closed a couple that are duplicates (and hence "not relevant"), and one of my own that has a perfect answer and needs no more feedback. But yes, I'd like some guidance on this too!
-
Time tracking is NOT a custom field. Start by fixing that.
-
I think that's right - flagging them somehow and adding them to an approval queue (Which you'll have to code for) is probably the way to approach this.
-
Then, I'm afraid the answer is no. Listeners are completely non-interactive, there's simply nothing to hang any form of user prompting on. In fact, I'm not too sure you can do it in any other way either. I assume you're looking for some form of acceptance popup when someone moves something on a GH board? I think that would…
-
Depends on how your plugin is doing it. Is it a listener of some sort?