Comments
-
I don't think this is possible - the time spent is calculated from the issue history from what I can make out.
-
There's nothing to stop people logging work and updating issues without being the assignee. And, as discussed before, there are plenty of ways of drawing many people into an issue. But you need a single point of ownership in real life, and JIRA only supports a single assignee.
-
I suspect Atlassian removed it because you should not have been using it as though it were a real user.
-
If you are talking about Cloud, then you were not using the Atlassian "system admin" account for logging error events because you have no access to it. If you are talking about a server installation, then you will need to talk to your administrators.
-
You can sort it by a custom field value, just add "order by <field>" to your board query, instead of "order by rank". But you won't be able to rank the issues if you do it.
-
Hmm. That's odd, as I can see the Service Desk type in the background, which tells me the main application is enabled. It looks like the project creation templates may have been disabled somehow, but there are other things that it could be. Can you try: * Go to an existing project (a temporary new one if you want) and try…
-
I don't know. Are they modules in the plugin? If they're disabled, it's probably for a reason. Are you using a valid version of the plugin now?
-
Your query, in English, is "all issues with a status of Done". What are you expecting this to do and what are you getting? Once we've worked out what query you need, the next question is "what do you want from the pie chart"? "A Pie chart for all projects" does not tell us what you want from it.
-
To create a project, you have to be an admin. You should not have to be a service-desk user to create a SD project, but it does mean you will be able to see and config the project when it is created. So, when you say "I can't create", what exactly do you mean? When you create a project, what options do you get in the…
-
It's a simple alphanumeric sort, and there's a way to change it without code. I don't know if you could inject some javascript to try to change it.
-
If you look at the marketplace listing for the add-on, you should see the compatibilities listed. Ideally, you should use the add-on manager to handle add-ons, that looks after versions for you.
-
Is your admin account (you?) able to use Service Desk? I mean, does it have the right permissions - in the applications list, there should be a group or groups with application access for SD, are you in one of thoose groups?
-
Please, read the article. Follow the link to the bug report and look at the fix there.I am trying to help, but you need to read the docs, I'm not going to parrot them at you.
-
I'm sorry, but this is very unclear. "A count of issues as a summary of something" is clear, but the something is not. Saying "restricted/undetiable/fixed values" is meaningless, you have not said what they are. Even just "values" wouldn't be that clear, although I'd assume you mean "values of a field". The…
-
Er, the bug has a clear fix in it. What are you reading?
-
Right, there was no way of knowing what you might be reading. Thanks for the link. There is a fix - follow the link to the bug. You'll find it is fixed in there.
-
It's "anyone who can log in" - so the users must be in one of the login groups (see global permissions) and marked as active
-
The two I've used are Ictime and Tempo
-
Is it the right version for your version of JIRA? If it's not, then you need to use the right one. If it is the correct version, then what do the logs say? As JIRA can't start the add-on, I'd say yes, the version causes an issue.
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/JIRA-Creating-or-Commenting-in-Jira-from-Email/qaq-p/594915 which has an answer
-
All the searches, here and on search engines, land on versions of https://confluence.atlassian.com/adminjiraserver071/creating-issues-and-comments-from-email-802592933.html
-
You will need add-ons to inject fields into the log work screen.
-
What's "symptom 4"? What docs are you reading? What version of JIRA is it, and what do the log say?
-
See the second option in my answer
-
Yes, it's just a warning about where to look for the issues if there are any.
-
Create an account for them, and give it the access it needs. JIRA doesn't limit users to organisations, if you need an external user, you can add one.
-
Ah, ok, that makes sense. Does "broken" mean displaying the __msg__ type name, or something else? If it's the __msg__ thing, then we've answered that, but if it's something else, you will need to explain it to us.
-
It's because transitions are variable, you don't know if the assignee is going to be offered. More importantly, it's not just transitions that might change assignee, there's the assign/assign-to-me and edit options.
-
It's not really Groovy doing this. The "def" bit is Groovy, letting you create an untyped variable to work with later, but the rest is Java calls into the JIRA AP. If you go to https://docs.atlassian.com/jira/server/ you'll see the java documentation for JIRA's API. In the code, you've got an "issue" object, so go find the…
-
Ah, that property is a step property, not a transition one. Try adding it to the "resolved" step in the workflow, you should see the assignee option list changes to your group when clicking assign or going through an outgoing transition with the assignee field on it.