Comments
-
It depends. The action of adding a user to a user picker could happen when an issue is created, edited or goes through a transition, so if your notification scheme says "notify users in the field when one of those three happens", then yes, they will be told.
-
Ahh, this is the fun of having ever-so-slightly different compressions and them being used oddly (not by you, I should say!) See https://confluence.atlassian.com/confkb/xml-backup-restore-failed-with-the-zip-file-did-not-contain-an-entry-exportdescriptor-properties-in-confluence-300811533.html
-
They're powerful, but yes, complex to negotiate.
-
If you need a clear alignment, you should have a clear single goal for the sprint too. Not different ones. You now have a place where five teams have up to five different goals to achieve with the same thing at the same time. What happens when the goals are not identical? People have the wrong priorities for others, and…
-
This should be a simple one - in the permission scheme for that project, you do not have "create issue" privilege for some reason. (Note, Admin rights means admin, it rightly has nothing to do with individual projects)
-
What do you mean by "activate"? If you mean "allow access for users who were disabled before", then whether they are logged in or not is irrelevant. If you don't mean that, then I don't know what "activate" means, or what "logged out" has to do with changing user settings.
-
No. That is explicitly what Jira Software is for.
-
This is, if I understand correctly, a move away from allowing any html tags because they've caused so many problems in the past. The removal of them IS the "fix"
-
Use Server, and have an admin who knows how to look after it. If you're on Cloud, you've deliberately chosen something with "holes", because the provider is not willing to let you break it to the extent you could with Server access.
-
Sharing, not really, but there are a number of Apps that provide "synchronisation" - this is where you connect projects in two separate Jira systems and although the issues are effectively duplicated in two places, most updates on one side can be replicated to the other. (This is not a flat copy if you don't want it - you…
-
This is a good place for help, but we're a community of end-users, not support. You'll need to start by describing what you need in terms of help, then we can try.
-
Yep, that's what I'm thinking of as "smaller companies", you often wear more than one hat. But that still doesn't mean the role of "admin" has to be to tied to "business owner of the docs" To go back to the original question, one of the things about software as a service (i.e. Cloud) is the aim to get rid of the admin as…
-
Nope, they've no plans to do anything about the 1000 limit. Gregor mentioned the REST API already, which allows for paging through the results.
-
You're right, if you want to do something different to the globally shared schemes, you'll want to spin off another copy of them to make the differences in.
-
Did you put all the "done" status in the LAST column on the board?
-
I'd call my familiarity "quite high" - I've helped Atlassian write their documentation, and that actually looks a lot like one of my quotes from when were talking about Jira 3.0 The problem I am having here is not my understanding of the product, the problem is that you are using words that don't make sense to me, or do…
-
So do I, when I'm given them. Let me rephrase this a little more strongly. The issues have gone from the "done" column for this sprint because you have removed them from the sprint. The fact I am working from here is that a search for "sprint = x" does not show the issues as being in the sprint. So they won't appear in the…
-
Please see Christian's answer from Jul 09, 2015 See also Andrew Heinzer's answer on why it's not an easy fix, and understand the point that although it would be nice to have it fixed, this is a low priority because it only affects admins, and only causes a few extra steps in a process for us.
-
You need to read the log file on the server to see why it is timing out
-
Add the clause AND NOT (issuetype in subtasktypes() and status in (x, y, z)) where x, y, z is the list of all the status in your "done" column.
-
Yes. You'll need to fix that. I can't help you, you have not told us what the error is. "Can not move" does not tell us anything. (At a long shot though, you've ignored "remove the transition screen" again, and removed the whole transition)
-
Ahh, ok, thank you. Edit the workflow in diagram mode, and the workflow designer will offer "new status" to you. Add "logged", then drag the arrow end of "logged excel & upwork" to any connection point on the new box. Add at least one transition out of it as well, or it will be a dead-end. You will then be able to run…
-
I don't think Tempo keeps them, and hence can't expose them over REST.
-
Yes. I don't see why you are quoting that at me though.
-
It's sort of telling you it is running out of memory. Start at https://confluence.atlassian.com/enterprise/garbage-collection-gc-tuning-guide-461504616.html to troubleshoot
-
So, you meant the switch from top to left menu, which has long been documented as irreversible.
-
There is no ""status" of resolution", that is a nonsense, and your workflow does not have a "logged" status. Please could you try again, and explain what you're looking for in Jira terms?
-
That's something that has been added to Jira by an App, I'd guess one of the risk-register ones. I think this will need to go to the support for that add-on.
-
What does the log file say the errors are after you restore and start it?
-
"Resolution status" is a nonsense phrase in Jira. Do you mean "resolution" or "status"?