Comments
-
No. I used "commit" to say "they complete the transition", as the next bit was about other transitions. For "create", it will be labelled "create" There is no "difference". The list I gave is the process that happens for create. I'm not sure what you saying what the "difference" is.
-
Think of the order in which things happen: * User clicks create * Screen is drawn * User enters data * User clicks "commit" * Validation occurs * Post-functions happen For the other transitions, it's much the same, but it has "check conditions" before "user clicks create". So you can see why post-functions are "too late".…
-
A post-function sets data after the commit to the transition (and passing of validation). That is far too late to "set a default", because a default happens as the user goes into the screen, and a post-function is way after they click "create" on that screen. So, I am a little muddled on what you are trying to do. Set a…
-
Yes. It's a bit of a nonsense to have a sub-task belong to more than one parent. They're for breaking up parents into more discrete pieces.
-
No, a subtask belongs to a single parent. Your use case is fine, but it feels like it has been reflected in JIRA really badly - the content areas sound like components, and "make change to X" should be a new discrete subtask every time you need to change it.
-
I'd enable the audit log, then you'll be able to track admin activities. ... and what Joe says - track the changes in JIRA with a JIRA project.
-
Custom fields do not go into jiraissue. When you say you are mapping this field - do you mean you are using a CSV import? Where you really don't need to even look at the database?
-
Have you looked at the "add condition" function in the workflow editor? Where there is a list of conditions you can add, including "only user in role", "only user in group" and "only user". I'm not sure why you're asking about scripting when there's all those options built-in.
-
A script could do it, but it might be possible with basic conditions or add-ons that provide condtions too. The main question is "who?". How are you identifying the person who is allowed to do the transition? Worst case, it's just "this person", but I'd lean towards "person in role", so it's flexible (and off-the-shelf),…
-
On Demand is generally updated on or before the release of the latest Jira. So the simple answer is always going to be "the very latest Jira you can currently download"
-
Get an account, then export your data and import it. Start at https://confluence.atlassian.com/display/AOD/Importing+Data
-
No, the point of roles is that they are global.
-
I think (but I'm not 100% sure) that if you raise a support request with Atlassian Cloud support, they will change the opsbar number for you. But you'll need to be certain what number you want, as they won't keep changing it!
-
I think this one is still in the "if it will be available" stages, rather than "when".
-
Oops, I forgot that one - I've not used it enough to remember it. Sorry!
-
There are no "project level" fields in Jira yet. Start at https://jira.atlassian.com/browse/JRA-1991 for the discussions, and there's a couple of plugins that can help - https://marketplace.atlassian.com/plugins/com.deiser.jira.profields is the obvious one, which works well. To answer your points specifically * Generally,…
-
If it's running slow, then one or many things are NOT in a "normal state".Bascially, you're going to need to do quite a lot of investigation here, it's not something we can fix for you. It's specific to your system.Start by looking at what you have changed recently - That is likely to be the cause of the problem. If you…
-
Could be anything - hardware, operating system, networking, volume of data, bad configuration, bad plugin configuration (or even just bad plugins) The question is what have you changed recently to slow it down?
-
Create a filter such as "project = X and assignee = currentuser()", save it, and then use it in a "filter results" gadget. The watched issues and assigned issues gadgets are just hard-coded versions of the filter results gadget that mean you don't have to create your own filter for it.
-
Not sure why getString even worked before, but try $component.getName() as the standard way to do it.
-
This is a complex one. Off the shelf, you can't quite do this by saying "make the field mandatory" as JIRA doesn't ship with the validators to check that the field is filled. You can install free addons to provide this validator. But you probably don't want to do it this way because there are better options: You can also *…
-
The users set up their own subscriptions, so get the users to unset them. (Admins can change subscriptions in later versions of Jira, but I can't remember which version it came in) However, you say there are no subscriptions when you look at the filters - that implies you're looking at the wrong filters if subscriptions…
-
Duplicate of https://answers.atlassian.com/questions/43205033
-
No, it needs the full key, as the uniqueness is pretty much mandatory
-
From the download page. Try https://www.atlassian.com/software/jira/download/ You'll want to have a read of https://confluence.atlassian.com/migration/jira-7 too - there's quite a lot of changes in 7 you'll need to think about.
-
Put the details in the global user settings for the repository (make sure the "enable sourcetree to update my config files" flag is set) Or just run it on the command line, all sourcetree is doing is reading what you've got set there and using it.
-
Run what it tells you to run and try it again.
-
Technically, no, there's no "resolution scheme"s. Your list of resolution is global. But, you can do it in the workflow. It's possible to add workflow properties (see https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html ) which can limit the options shown to a user when going through the…
-
Worth a try - at least it's good to know it's limited to the components field, and that probably rules out any code (css, js etc) that they share. Definitely one for Atlassian now I think!
-
Another good idea for something to try. At this point, I'd be reaching for Atlassian support, although there's a couple more (rather forlorn) ideas to look at if you can: What happens if you add a multi-select list (with at least 2 options) to the create screen, temporarily? Does that work ok, or fail in the same way? Go…