Comments
-
You're right - a user will have to identify themselves somewhere. My guess was that "internal" users would be logging in with internal SSO or something, that's why I asked about the current authentication and identification system.
-
Probably, but it depends on how you are doing authentication and identification at the moment?
-
If you want information, it helps if you actually ask a question. As it is, my best guess at an answer is "buy a licence, upgrade to 3.5, then 5.0, then 5.5, and read the documentation on how to do that"
-
The attachments in Jira belong to the issues, and hence are subject to the same security and permissions. To make them available to people outside your organisation, you'll need to expose the issue to those people - this can be done by making the issues available to anyone. But it really does mean anyone. You've got other…
-
Start with a close look at the difference between his account and one that is working ok. Groups, project roles, profile settings and what browser he's using (can your working user try his machine?)
-
You'd need to edit the template that builds the content of the email.
-
* Run a filter for something like* updated < -1h and resolution is empty * Save it * Subscribe to it and put it on a regular cycle That filter will regularly email you a list of all issues that are unresolved and have not been updated for over an hour.
-
No, nothing new, other than "write your own clone function"
-
Yup, but that's coding in the core of Jira...
-
Note that this also clears out fields if the users enter them when creating a new issue in that project, so it's only appropriate for fields that you don't want to use on the creation on a new issue.
-
Yes, you're always able to renew support, and yes, a renewal is always the 1/2 price.
-
Yes, you're always able to renew support, and yes, a renewal is always the 1/2 price. The only time you don't get the 1/2 renewal is when you let your licence lapse for a while - then you need to get a full new licence.
-
I'm afraid "growing teams" is just the description for "you fall into the middling tiers for number of users" The licence model doesn't change - if you want to maintain support and upgrade access for JIRA Software, you will need to renew every year. The "one time payment" means the same at all user tiers - you get a year…
-
If you mean licence keys, no, you don't need to restart. If you mean ssl keys, then yes, as the jvm needs to reread them.
-
No, you can't change them. The attachments field is the way it is because it needs to be (changing it to text would be pointless as it wouldn't be able to handle attachments any more). The simple solution for that question is to disallow attachments and add a custom text field.
-
I don't know, it's not something I've needed to do.
-
Ok, I'd recommend a very strong warning before just doing this in your add-on - be clear "If you confirm doing this, you will destroy all your ranking information that you've been doing in backlog grooming and planning, for the entire team" Your Connect add-on will need to use the REST endpoint - I found…
-
The backlog takes the sort order from the filter for the board. So, there's basically two ways you could sort by another field - change the filter to have a different sort order (which breaks ranking because you have to sort by rank in order to rank things), or update the issues by re-ranking them all in your new order…
-
I'm not sure that a Connect add-on can get to the sort order on the surface, and even if it could, the best you can do with it would be to remove the ability to rank issues. I'd recommend not trying to do this, as ranking is quite important to backlogs.
-
If you can see a filter, it's either shared with you, or it's yours. In both cases, you'll be able to see the sharing in the filter descriptions. You STILL haven't explained what you want from these folders - the results of filters, or just the definitions. I'm going to assume the definitions though - you can't arrange…
-
No, Jira's queries are more flexible than that. A release is just a case of using a clause that includes the release(s) you want. I still don't quite understand the "store a query" - do you mean the query defintion (a "filter" in Jira can be saved, shared, modified and used in loads of places. Or kept private), or the…
-
I'm afraid saying "folder" instead of "group" does not explain what you mean. What are these groups/folders/penguins? Where are they? What are they for? What do they do? Most importantly, what are you expecting Jira to actually do with filters and these things?
-
What do you mean by "group the filters"?
-
Sorry, I wasn't clear. You can share with no-one, or a group or role. Or "Everyone", which will even let anonymous non-logged-in users see it. Anyone who can create shared objects can create shared filters (this is controlled by the groups named in the global permissions - a lot of sites set it to "jira users", which…
-
All filters are read-only to all but the person who owns it. Admins have rights to change owners though. But people can start from a shared filter and create their own.
-
Yes, there's something not quite right in your database server setup. I've seen "(Unable to esablish a connection with the database. (Could not create connection to database server. Attempted reconnect 3 times. Giving up.))" a few times before, and it could have several causes. Unfortunately, it's always been a DBA who's…
-
It still looks like your best bet is to create a new project and then move the issues with bulk-edit. I'm not sure why you'd want to do it any other way - a bulk move will retain all your data and history, links back to the old project where the issues were and really is immensely easy compared with the other methods…
-
If there's a permgen problem, it's likely other parts of Jira are failing, the plugins will never update and it will definitely show in the logs (which you might want to check anyway)
-
Yes, exactly - it could be the plugin needing to do stuff as it upgrades.
-
You might want to take a look at your hardware and profiling then.Some plugin updates are heavy on the resources because they have to be - they may be large and have data to check and update. Smaller simpler plugins, and ones that don't have much data don't place a significant load on the machine while being updated.