Comments
-
Technically, it will handle huge numbers. Way more than your users can cope with. For components, keep it simple - your users simply won't cope with hundreds of options. For versions, your users will be thinking about them differently and it could be fine to have thousands.
-
I think you need to explain your question a bit more - most of us won't know what "folio" is (I can take a guess, but I'm not certain I'm right) and what part of it you are trying to use.
-
No, I don't think the webhooks warning is a problem. If the message goes away after you've done the re-index it wants, then I'm not sure that there is any problem here - you've made some changes that make Jira think it needs reindexing, you do the reindex, and then all is well. Is that right?
-
Mmm, that's a bit cryptic, if it is not telling you which module has changed externally. I don't think it's the upgrade, but the config of whatever the external module is.Is there any more information in the message? Does it go away if you go ahead and re-index? Can you check the logs to see if there are related messages…
-
Nothing wrong, but it's nothing to do with your backup cycle either. JIRA asks for an admin to re-index when you make certain changes in the administration side - almost all of the triggers for that are changes to custom fields. The message it gives to admins should indicate roughly why it wants a reindex - it will be…
-
Have a look at https://www.atlassian.com/experts/search?page=1
-
Nothing to do with Atlassian then.
-
What has this got to do with Atlassian products? They're not php based, so I'm a bit lost on what you're doing.
-
So it's not adding items at all, it's the order the existing ones appear in. I'm not quite so sure how to do that. I'm sure the priority order of options is set somewhere, but I've not looked at this in enough detail to tell you where to look, sorry.
-
Mmm, that's not what you asked - you explicitly mentioned workflow stuff, rather than "actions". Anyway, those actions are not part of the workflow, you can add more by writing or finding "webwork modules" to add to the list. See https://developer.atlassian.com/display/JIRADEV/Webwork+plugin+module
-
I don't think it can. What Jira is doing is presenting the user with a list of things that they can do to the Issue, outside the workflow (Edit, comment, delete, etc). It filters the list through permissions of course, e.g. comment won't be there unless the user has comment permission, so if you're missing an option, check…
-
I suspect you might be asking for something else, but the answer to your question is just "Edit the workflow to add what you need" - see http://confluence.atlassian.com/display/JIRA/Configuring+Workflow If it's something else, could you explain in more detail what you're trying to add?
-
"Teams in Space" is a demo system Atlassian use, and allow partners to use for general demonstration, documentation and experimentation work. It's not a test or training system for end-users, and it's only available as a download-and-run-it-yourself system for Atlassians and partners. The documentation is expecting you to…
-
You can add validators in the workflow. Screens are actually pretty much irrelevant when it comes to mandatory/optional settings. The giveaway is the missing red * when you do add it to the screen. If there's no *, then it's not the field configuration setting it mandatory, it's a validator in the workflow.
-
Yes.
-
You'll need to find or write a report to do this.The closest you'll get without coding is separate reports - search for L1, 2 and 3, and put them in one gadget, and then L4, 5 and 6 in another gadget, and so-on.
-
You can't. A row and a column will, by definition, show all the data that they have from the query.
-
The context for a field (associating with a project, or even issue type) is about whether the field is used by that project and issue type.Field configuration has flags for the renderers, mandatory/optional and the ability to hide fields. I'd say all of that can be better done in other places.
-
Well, to be fair, there's nowhere else to set "field is mandatory", it's all done in the filed configuration stuff, so I'm not sure I'd call it fruitless, distracting or a placebo. But I would go with "as confusing as a talking aspidistra turning into a teapot. Gronda Gronda Rangdo"
-
I've always felt that the field configurations should be binned and merged in with the other two things you have to deal with.
-
The field configuration for the two projects is different. One says the field is mandatory, the other says it's not.
-
Yup, it's the same answer. Forget screens. Look at the field configurations.
-
You don't. Why are you looking for it?
-
You've said that, but where are you renaming them, and is it a clear pattern?
-
Ooh, "input ignored" is a really unusual message! I don't think I've ever managed to make Jira say that to me.At least the behaviour is consistent with the error. I think this is definitely one for Cloud (OnDemand) Support. Although before you raise it, I would do another couple of things - first see if you can get a clear…
-
Seems fine in the OnDemand/Cloud systems I help out with. Two things * What issues are you actually getting? (Error message? Input ignored? Friendly penguin interrupts you every time you click "edit"?) * https://support.atlassian.com is where to raise the issue if we can't help you
-
Um, this isn't Atlassian support, it's the user community. We can try to help, but we're not "support". My insinct is to look in the logs for other errors that may be corrupting the issues, not just the GH one. And to test if re-indexing fixes it temporarily or permanently. And check the workflow in the affected project -…
-
Ok.Yes, lots of people do that, and adopt Atlassian tools afterwards.
-
A three letter question? Not enough to go on there really.
-
My understanding is that the latest version will take account of that, yes. (Older ones with the non-dynamic planning did not until quite a later version if I remember correctly)