Comments
-
Sprints burn down when stories you commit to are done. Not when bits of them are done. There's a load of stuff above (and in other conversations) that covers that, as well as explaining that Atlassian have taken the easy route of doing burn down properly by ignoring sub-tasks.
-
Ok, so this tells us your "regular" email address does not have a Bitbucket Cloud account. When you enter the account name, it is already "taken", so you need to log in with the Cloud account it it belongs to (which is obviously not your regular email address). You'll need to go through the forgot password / account…
-
A slight expansion to that - Apps are installed in the Jira Core framework, not in the Applications that they add functions to. There's nothing in Jira that says "this App belongs to that", it's all up to the App to say "hey, I require this" and "I'm only going to work here".
-
Those macros are hidden because they're not supposed to be used (directly) by users. To move them out of hidden, you would need to find the properties that classify them that way in the code, change it, recompile the Apps that provide them, and then explain how to use them independently to your users.
-
Have you tried doing what the docs say at https://confluence.atlassian.com/doc/multimedia-macro-228622735.html
-
Ah, ok. Your language mislead me. You said " a new field i have created called security level" - you did not create a new field. You created a new "issue security scheme" which uses a system "field" referred to as "security level". This field does not appear in the simple search drop-down. It does appear if you used…
-
My father and I both do. He's got a couple of old battered tin teapots he's used since I stole our old one when I left home. I managed to break that one and modernised. I now use an "infuser" pot (left) instead of a "proper" teapot + strainer.
-
Ah, neither. This is where there is no "positive" answer. There is no REST API to move an issue. So there's nothing you can do here directly. What I was talking about was the Java API internal to Jira, that you can call in scripts and Apps. The best you can do with REST is get a copy of the issue to be moved, then write…
-
Scroll down the page, it's lower in there. Or look to the left and click on "workflows" in the admin bar.
-
I am completely lost then. If the field is not in custom fields, then you did not add it and can't use it. Could you explain what you added?
-
Not quite. That would defeat the purpose of having a wiki, it's supposed to track all changes! But two things: First, for the notifications, look at the bottom of the edit page. There's a box for "notify people on minor changes". Setting that right will stop emails going to watchers etc. Second, you say your changes are…
-
My other half drinks her tea somewhere between "warm" and "room temperature". 15 years, I love her, but still, ugh.
-
Ok, here's the positive version: Your code will need to check that the new project and issue type configuration matches the current issue for * Workflow status * Every field's * Mandatory/optional * Visibility * Context * Security level (I'm pretty sure this is not an exhaustive list) In the cases of mismatches, you'll…
-
Perfect, thanks for clearing that up for my Friday-addled brain! There are a few reasons it might not appear in that drop-down. * It does not have a "searcher" * It is of a type that does not support a simple search * There are criteria set in the system fields that rule it out from appearing because it is not valid for…
-
I think you are mixing up status colour and column colour (this is not an obvious thing from the docs, and I don't think the UI even mentions it, so I'm not surprised if you are). Each status has a "status category" which determines the colour of the status - grey (none), to-do (blue), in-progress (yellow), done (green).…
-
Yes, Cloud does not have those services because it does not need them, as Cloud does it differently to server, or they allow you to do things that Atlassian do not want to support you doing in their managed service. The documentation for Server is often not appropriate for Cloud, so bear that in mind when you're reading…
-
Set the listener to look for all events where someone might blank it out (probably "issue updated" and possibly events in your workflow if you've got transition screens for them) In the event, you'll be able to get a handle on the issue, where you can then say "if the value changed from <something> to <null>/blank, then…
-
When you say "search filter" - where do you mean? For example, my brain rattled off a list of places: * In the drop-down on the simple search in the issue navigator * As a field on offer when typing JQL into a complex search * In a gadget field selection * On a quick filter for a board I'm sure there's more it might apply…
-
issue.getCreated() should return a date/time stamp with that data. I'm assuming you already have the right issue object to work with. (e.g. in a post-function, issue is directly available as the current issue)
-
> I want to be emailed immediately when that happens This is what the notification changes given in the original answer does. Andrew's answer gives you the additional option of subscriptions, which are a bit more flexible about what you can subscribe to, but only on an interval and gives you a collection of issues which…
-
Yes, it sounds like you still have damaged indices. You'll need to establish what was happening that broke it before, and then you can establish what to do to fix it all. Please, don't just randomly pick another possible problem and attempt another potentially pointless fix before you've looked into this properly. Now…
-
Not sure why you did that when I've never mentioned it, but that does explain why all sorts of things are missing - Jira needed those files, and you've destroyed them. To fix that, go to Admin -> Indexing, and run a full, locking index. If the underlying problem you have is disk space, this is going to go wrong as it…
-
This is something I really don't find obvious in the docs or display. It is about filter ownership and defaults. Note that "search" and "filter" are different things. First, look at the issue navigator - you run a new search, you adjust the fields on display, change the search and so-on. You get what you expect, I think.…
-
Ok, great on the database, it means it's almost certainly not a database problem. For the space and permissions, you will need to log into the server and look at the disks. How you do that is up to the OS and what access you have to it.
-
You have a string of rather worrying errors there. * The attachment error implies something wrong with either the file system or attachments area of the database * The end of life warning means either you have an out-of-date Jira, or that it cannot reach the internet to check (this one, don't worry about for now) * The…
-
Ok, that is what I suspected then - the division is resulting in an output that does not work for loading the field. The /1 returning a failure is consistent with that! My guess is that there's something like a type conversion going wrong - if for example the output of a division is a float, and Jira only (usually) works…
-
Sort of. If you take one of the more popular brands of tea-bag, you'll find they're standard black tea. Making a mug or cup of tea with one of these brands is often called "builder's tea". Because when you have workers around your house, and you make them tea, it's one of the brands, tea-bag in the mug. (And usually strong…
-
I'm English. Tea is built in. ;-)
-
To move issues from one system to another, you will need to perform a full migration. Same for the Zephyr data (and I don't think that's possible to do in full).
-
You'll need to ask the vendor for it. Often, the source code is closed and commercial, so they will not share it.