Comments
-
There are no system requirements for these individually, as they are Apps you add to a Jira system. If you need something to say "we might need a bigger server if we install these", then take a look at the hardware requirements for Jira, and depending on how much you plan to do with the Apps, simply add some users to the…
-
You can do it, but it's torturous, has side-effects and hence might not do what you want. If you edit the workflow, and look at the step the transition goes from, there is an area for "workflow properties". You can add a property that blocks the permission to comment. This will stop the comment box appearing on all…
-
I don't think there is a way to do this on Cloud. On Server, I'd use Scriptrunner to write a condition that looks at the sprint field and blocks transitions if it's not the right sprint. But we can't add conditions to Cloud (yet)
-
I seem to remember that there are a number of improvements logged to do with labels, including a "rename existing", but Atlassian don't have them high on the to-do list. I suspect it's partly because the labels field is not like select lists and "renaming" a label would be a "search and replace". With a select list,…
-
No, an administrator's job is to look after the whole Jira, they have access to administrate everything. You should not have lots of global admins, but you should consider delegation - if you have Jira Software, simplifying workflows enables project admins to amend their workflow. You can also delegate some workflow admin…
-
Check admin -> applications
-
Burndown happens when you move any issue at the level of Story to "done". So as long as your Tasks are at the same level, you can add the estimation field to them and they will burn down like stories.
-
Have a read of https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
If you have Software on Cloud, then install Software. If you only have Core on Cloud, install Core. The link for downloads is on the download page for Jira. Any search will take you there, I'm not going to google it for you.
-
You will need one of your site administrators to re-enable it.
-
I'm afraid you have "fielditis", which makes the list long and unweildy, but there is nothing you can do about it other than try to reduce the number of fields you have. (You could help by a bit of a redesign - most of the fields in your screenshots almost certainly should be status, not fields).
-
Could be anything. You'll need to tell us the context in which you saw it, and even then, probably ask the people who are using the phrase!
-
A subscription runs regularly, so it will not do "notifications when the issues are updated" - that is specifically what the notification scheme is for. (And to do it with notification schemes, just add "Reporter" to the events they should be told about) But if you want a subscription, then a filter for "reporter =…
-
Ahh, I see. There's definitely a problem here, but I don't think it's Jira itself and I'm not sure it's a "bug". I'd take a guess that Tomcat is misconfigured or something in your network routing. The reason I say that is the evidence could be paraphrased as: * Jira responds on the correct url * Browsers are telling us a…
-
I am a bit confused - you say "at some point in jira i had set up this group manually, instead of it being synced from the domain." then " but it probably is syncing from AD" I think we need to start by establishing where the group is coming from - is it AD or internal (or a third directory)?
-
No, the view of an issue is determined by its project and issue type.
-
You can't - the point of a sprint is that you draw in the top-ranked issues.
-
I assume you are setting the departments with a field like components or a custom field to put it on each issue. Two steps to this - first, run a filter for the issues you want to see ( "created > -1w" for example) and save it. Second, use that filter in a dashboard gadget. The most simple one is probably "filter…
-
Not directly. Jira Software's definition of "done" is "in the right hand column when you end the sprint". So, if you want a certain resolution to be ignored, you either have to drop it from the board, or set up the workflow such that the only way to set that resolution is to move the issue into a status that is not in that…
-
Hi Carl, and welcome to the community. The simple answer is because a board is not a project object. A board could include issues from different projects. A project is the container for the issues, not the board, and that's where all the configuration is done. A board is a view of a set of issues, taking the status it…
-
Hi Nermin, and welcome to the community. I'm afraid I only have half an answer: 1) What is "split on module"? 2) Have a look at the "created vs resolved" gadget. This is exactly what it is for!
-
No, actually you can't change the domain (yet) You can buy a new one and migrate to it, although it will still be <something>.atlassian.net
-
You need to set (and clear) a resolution whatever you do. If you don't want to ask the users for it, remove it from the transition screen you have found it on, BUT, remember to add a post-function to set it to a value, otherwise your reporting won't work. As Joe says, you really need to remove it from create and edit…
-
Move one or more of the status into the new columns. Columns are simply collections of status. If you want to add more status, then talk to your admins - you either need: * them to edit your workflow to include new status * them to set your workflow to "simplified" (you'll then get "add status" near "add column" in the…
-
Try adding the applications by searching the marketplace, rather than uploads.
-
Yes, that is what Alexey said.
-
Go to the project config and swap the "workflow scheme" to another one (you can create a new one for this, or reuse an existing one)
-
The -D flag is (or was?) a "dark feature" which it is recommended you do not use. The system I saw it in was a few years ago, and it may well have changed or been removed. I can't find the document it used to be noted in anywhere, which means I can't tell you what the flag was. It was something reasonably obvious, as you…
-
You will need to debug your external network routing - your symptoms are of a a request reaching the server, but the network not returning the response to the client.
-
You will need to talk to the admins/owners of this eBay wiki. We're end users of Atlassian software, and have less access to your wiki than you do.