Comments
-
Are your administrators showing loss of any other admin rights?
-
You need to add the "estimate" field to the "view" screen for the issue type. (Bear in mind that Jira does not display fields that have no data, so you need to test this with an issue that you have filled in an estimate for) See https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens
-
Board views don't support tabs at the moment, so you can't do it.
-
Yeah, I scrubbed it, it just wasn't fast enough to be usable.
-
Work - technically yes. Usable - pfff
-
It works, just, on a Pi2 B+ and the instructions are: * Install something like Dietpi so the OS is utterly minimal * Use an external USB drive * Install Confluence as per instructions for a Debian based system (Assuming you used Dietpi) * Before the bit where you first run it, edit setenv.sh, lowering the maximum memory to…
-
If you think this is a bug, have you raised it with Atlassian support?
-
No. Neither can be removed. Description can be made optional, and then removed from all screens and even hidden in the field configuration screen. Technically, it's still there, but practically, it's gone. Summary is mandatory. End of story. You'd need to rewrite a chunk of the core code just to make it the same as…
-
The back arrow won't work - you'll have been through two screens for a start, and the one in the middle will be prompting you for data, and the context of the original screen may have been lost by the act of visiting the new issue screen as well.
-
It used to do that all the time. So many people complained about it interrupting what they were doing, Atlassian moved it to a popup so you didn't lose what you were doing! I do understand the desire for different behaviour for different ways of working - I remember asking them to make it a profile option so that an…
-
You should write the script in whatever is most appropriate for your server and organisation. If you write it in Java, you'll need to write something that can connect to Jira, extract the status information, parse it and be runnable by your subversion service. I've only ever done commit hooks in shell scripts to be honest
-
I don't know enough Perl to help you here. It's very good that you've raised https://answers.atlassian.com/questions/102032/how-can-i-include-the-status-from-the-issue-in-the-commit-acceptance though - a new question for this will get a lot more attention than this comment! :-)
-
Then change the SVN script to use status, as previously suggested. Your script is making inaccurate and unhelpful assumptions about the way Jira works. You have two places you can "fix" this - there's either re-writing a huge chunk of the core of Jira and potentially any plugins that look at issues, or you can fix your…
-
Er, yes, that's because you're choosing to break it. As has been pointed out several times above, Jira considers an issue "resolved" if there is ANYTHING in the field. Doesn't matter if you've filled in fixed, null, fred, unresolved, Mr Flibble - the system is asking the question "is there data in the field". If there is…
-
I'm a bit lost - you've got a clear error with your regular expression, followed by a "cannot connect". You need to fix both of those. You're not telling us what you've done to the script, where you've inserted Renjith's code or how you've changed it to match your requirement. I've already pointed out that the connection…
-
Don't know. Where did you get the script? What's it doing? What do the logs say (on both sides?)
-
You've got two - the second one MIGHT be caused by the first (I don't know perl well enough to tell you if that's the case). The first error is in the regular expression you're using. The second a connection error. Pretty much what the error messages are telling you - your code is wrong, and the connection possibly broken.
-
Ok, well, that explains your svn problem - the index and the issue are not matched - that's going to break all sorts of stuff! Next thing is to fix that. Can you try moving the "update resolution" to the same place as "set approved to no" and retest the search/view mismatch? (Oh, and check for mismatches in that field…
-
Ok, good, if they have the permission, that rules out one potential problem. The explanation of why you want "closed" issues to be created doesn't feel right to me as a usability thing (as Joe pointed out - there's a lot of stuff in Jira that says "ignore resolved issues because they're technically dealt with and don't…
-
Yup, I was assuming Fabio had understood that any issues created with this would be automatically considered as "closed" by most of Jira. I shouldn't assume that people know this stuff...
-
Does the user creating the issue have the "resolve issue" permission?
-
Difficult to say, as that information is not gathered by Atlassian (they may well ask, but it's voluntary and ignored). You could ask them about stats for "database usage you see in your support calls", as they do ask when you raise a call, and there's no reason for someone asking for help to lie. But I suspect that would…
-
That's the problem, we don't know anythin about your CMS either. We can tell you about Atlassian products, but we're not here because we use others. Confluence can use all sorts of user directories, including many which will support SSO, but on Cloud you only have the Cloud users or Google accounts. So you'd need to make…
-
How are you getting your PHP Drupal system to read the Confluence Cloud user base?
-
>The default was that every user had access to everything meaning some clients could see projects they shouldn't. Yes, I'm afraid you will want to unpick that. The usual problem is that the default is to add users to the group that says "can log in and use the system", but that group is also used in project roles to say…
-
Sorry Aron, missed the email update.I just rummage through Jamie's docs for examples - https://jamieechlin.atlassian.net/wiki/display/GRV/Script+Runnerhttps://jamieechlin.atlassian.net/wiki/display/GRV/Post+Functions+With+Comments might be a good start though, as it's got custom field code and some stuff around users.
-
Script runner. Always.(I'd have said that before either Jamie or I joined Atlassian, it's the one I've always turned to when something "clever" is needed)
-
You'll need an addon that provides such a post-function, or one of the scripting options like Script runner. Once you've decided which route to take there, then we can probably help you (although it's "get user, put user in field" really)
-
Make sure you have the "delete issue" permission in the permission scheme for the project, and the option will appear on the "actions" menu. Be aware, delete is done properly - the only way to "undo" a delete is to recreate the information from a backup
-
That's the point - to do it within Confluence, you have to have a mechanism that allows Confluence to identify when a user is inside your network.There are so many variations possible on this, there's no way to code a generic approach, and the vast majority of Confluence users don't need it anyway. So there's nothing in…