Comments
-
You can't really do this. A field is either on the screen (and hence edit-enabled if the screen is an update of some sort) or it's not. A couple of the system fields have some permissions around them (e.g. assignee only appears if you have assign-issue permission, fix version only appears if you have resolve), but they're…
-
See https://jira.atlassian.com/browse/JRA-3156
-
Correct, you have to be a system or Jira administrator to edit a workflow. You can't delegate it further down. Yet. Atlassian are looking at delegation of admin functions, although there is one honking great issue with letting project admins change a workflow - they're shared, so an edit for project X could break project…
-
As I already said, no, you can not change what permissions are available. It sounds to me like you have given this user "JIRA Administrator" rights. But they are asking for system admin rights, so you need to put them in the system administrators group instead, if you want to grant them all those system rights. As it…
-
Correct. Admins get admin rights. That's it. If you could alter the permissions, then it would be an admin who did it, so they could add/remove whatever they like. So it would be utterly pointless. What Atlassian are looking at doing is more delegation, so an admin can enable non-admins or lesser admins to do more of the…
-
Not yet. See https://jira.atlassian.com/browse/CLOUD-6999 Similar for the email server - you can't use another server for outgoing mail, but you can get JIRA to read incoming mail from your server - see https://confluence.atlassian.com/display/Cloud/Creating+Issues+and+Comments+from+Email
-
You can't. OnDemand has a fixed list of plugins that Atlassian will allow you to buy and install. If it's not on that list, then you can't have it. You can try asking Atlassian to add it to the list, but the list really does grow very slowly. No harm in asking. You could hang on a while though - they are planning to…
-
It's not a field in JIRA, it's pulled in from the user management stuff - you'll need to change it in there.
-
So are these requests with you, or Atlassian?
-
What sort of thing were the last updates on the issues you've raised at support.atlassian.com? Status updates? Feedback? Questions?
-
It sounds like you've locked down filters that were in use on the other boards. You'll need to make them visible again. For the manager, create new private unshared filters.
-
Code. You'll need a post-function that can scan through the role and select the "next" user according to your round-robin rules. See https://developer.atlassian.com/static/connect/docs/latest/modules/jira/workflow-post-function.html
-
Exactly why I pointed to it - your answer there is pretty much what I would have said too :-)
-
No. A filter is for finding issues. Off the shelf, I'm not aware of any queries that would find you "issue where transitions from A to B > #", there may be some in plugins, but even if you find something to help you filter, it is not going to help you report on it. Filters find issues. They do not extract information from…
-
This has almost exactly the same answer as your other question - https://answers.atlassian.com/questions/185672/of-times-fixversion-moved-to-other-version (Yes, the questions are different, but the answers aren't)
-
What user directory are you using? Crowd, LDAP, internal etc? For a JIRA using it's internal directory, there's nothing that would delete a user without an admin actively doing it, so it's either an admin or an addon doing it. I'd recommend enabling the audit log to see if it can capture the account that is removing them
-
I wrote a plugin to solve this with a derived field, ages ago. I really should dig it out and publish it.
-
You'll need to work through the same process as above - what *exactly* is the configuration of the email handler. What *exactly* is the subject of the email you think is triggering the mail out, and when is it happening?
-
So, it's not "reusing" numbers at all. It is responding with an email referring to an old issue, and not creating a new issue (not quite the same as the original post, but close). In other words, "A Ticket mailed in last night was assigned issue number of SYS-9185." is not true, you are getting an "issue created" email…
-
I have read it, and it is totally unclear. Ignoring requests for clarification is not going to get you any help.What does "reuse" mean? What *exactly* is happening here - you send Jira an email, and you get what? I can see you get a response mail, but what does "the ticket gets lost" mean?What mail handler are you using?…
-
I don't understand the question - you can't "reuse" numbers in JIRA, they're unique. What do you mean by "reuse"?
-
Of course there's a "latest" counter for a project, but it's nothing to do with email. Neither is the database-id counter. If the email is going to create an issue, it uses the same process that the UI does. Or REST. Or the listeners and post-functions that create issues as part of the workflow. I'm not sure why you keep…
-
Ok, that's all narrowing it down a lot. Next question, based on those - is it always EXTEL-1059 you get a mail for?
-
Hmm. I've got a sneakily horrid idea on what it might be doing, but before I ramble at length, I should check a bit more. You mention EXTEL-1135, which I'm not sure about. Could you confirm that no new issue has been created at all by this email? In ANY project? Secondly, does EXTEL-1059 have any comment added to it by…
-
It gets a new number in exactly the same way create issue via the ui does. I think the problem is before the create, it's the decision on whether to call "create" or "comment", it's never getting to "create" because it's picking up the email as a comment. I'm not clear on exactly what you are seeing here though - could you…
-
Jira's standard incoming mail handlers look for an issue ID in the subject first. So if you send Jira an email with something like "About that Jira issue ABC-123", then (assuming ABC-123 is an issue) it will attach the mail as a comment. If it cannot make that association, then it creates a new issue in the project you…
-
That's not something you do in a standip
-
No, you don't. A scrum master does not need to enter invalid information by impersonating users. As an admin, it can be useful for debugging, and there are "su" type add-ons that allow you to do it (although the option is a poor substitute for understanding a system better), and Cloud lets you do it too. But they are…
-
I'm afraid there is no easy way to do this. You need to work through the permission schemes to work out each rule and then add your user to the appropriate group or role. (Note - I recommend the use of roles as they let you have simple permission screens and allow you to add users to specific multiple projects quite easily…
-
Mmm, that still doesn't really explain what you've done, but it's worth trying to simplify. Forget about defaults. Go into the screen scheme and explicity say "View = Screen X", "create = screen Y" and "edit = screen Z". You might only have two screens and are using one of them twice, that's fine, but make it explicit, so…