Comments
-
That is very true, but Kanban has a poor model in using "done" repeatedly. This does not fit with any useful workflow, and JIRA requires you to separate them properly because two "done" status is confusing and simply doesn't work in a logical workflow. (Ask three of your humans if something is "done" and when they see it's…
-
Please see the answer I gave already. (If you mean "the activity stream", it's not stored, it's extracted)
-
It doesn't handle it well, but the problem is that because your user can't see the issue, the link should not be followable The only way to allow it is to make your JIRA publically readable.
-
You need to read * the configuration docs for the version you are on * the configuration you currently have * the new docs for the version you are going to There may be little or no change, but you may need to upgrade the database. You should use the instructions from the database vendor to do that.
-
The development system set up by the atlas-... commands is a bit different to a standard JIRA server. There is no "development environment" for a standard server system. You can use atlas-cli to deploy your compiled add-on to a remote JIRA server, but the build should be done in your dev system.
-
Ok, it's definitely time to read the logs then. What does clicking "update" throw into them?
-
You'll need to implement it as four columns if you want to see it as that (there's no "sub columns"), and ensure you have a single proper "done" column. Everything else in that spec is workflow conditions and validators.
-
Could you explain what this "jira XML file is"? Where do you get it from? I don't quite understand your second paragraph, or what you're trying to do, but I do want to point out that "using API calls" strongly suggests that you should be calling JIRA's REST API, rather than messing around with xml.
-
As Thomas says, it's in progress. Ways to better watch and support our add-ons in the Community is very high on the list of improvements.
-
What does "track" mean in this context? You can see the issues by looking at the board, but I suspect you want more than just that?
-
What do you mean by "default Tempo time sheet report"? Which one is it?
-
Ah, hang on, that's slightly different. "Cannot edit" to me means "the option is not there", and that's what the properties would do. What you're seeing is that you can start to edit, but not complete, as the "update" button does nothing. This implies possibly a failed validator with a broken error message (it should tell…
-
Hmm, it seems like we've lost a chunk of this conversation, but there's enough to con Ok, that's good, although it should not be being run as root (check the script user.sh in the same place as start-jira.sh has the right user name it in, then make sure that user owns all files and directories under the jira installation…
-
Labels and text fields are standard field types in JIRA, you can just add them to the "create" screen, and use them, no need for code. See https://confluence.atlassian.com/adminjiraserver073/project-screens-schemes-and-fields-861253368.html
-
The best way is going to need a little code (i.e. an add-on that implements some code, or a scripting add-on etc). All you need is a simple condition though, one that looks at the number of comments since the last status change and blocks any transitins when it's less than one. A more simple option might be a validator…
-
There is only one way to set up JIRA to prevent "edit" in some status and not others, and that is with workflow properties. Have you checked the permissions are set to let you edit? Could you also check for properties on "open"?
-
This sounds like the workflow may have had "do not edit" properties added to the status. Check the step/status properties on the workflows. I think it's something like jira.issue.editable.
-
You'll need to write a new field to do this, one that understands the relationship in full.
-
Sorry, yes, that issue.<function> is wrong. How you get the list of links is highly dependent on where you are in JIRA, but you'll probably end up needing to use an issueLinkManager - see https://docs.atlassian.com/jira/7.3.8/com/atlassian/jira/issue/link/IssueLinkManager.html
-
NO! Never do this, it's an utter disaster no matter what you do. A validator should make NO changes to any data. It should return either "True" or "False" and do nothing else.
-
Patrick has it right on the nose. All the docs say to apply properties to the transition, and that does work. (Sorry, I didn't see the comments earlier, as Lithium's email system was broken until more recently)
-
No, a comment belongs to a single issue. You'd need some code to follow a link and pull comments from other issues (and it could be quite horrible to display because issues can have lots of comments, and you'd need to think about how to handle many links)
-
Note that some add-ons don't need a licence, and therefore don't have the licence box to paste the key into.
-
The formal answer is "not a lot". The best answer is based on a bit of interpretation of your question. I am guessing you are asking this question because you aren't sure if you should run it on Linux or Windows. In that case, the answer is "You should run it on the system you know best". If your organisation runs a lot of…
-
Yes. The JIRA system you have should gracefully allow you to use a server licence for it, and drop all the DC related stuff.
-
Sounds like it was trying to add something into the summary. Glad you found it!
-
Please see Thomas' answer and follow-up, those are the functions available to you.
-
Yes, you can allow your Core users into them, but you won't get any of the functions of Software.
-
Good point. I don't know if Gaia uses any of those templates.
-
Ah, sorry, you talked about "child" issues, which means "sub-task" in JIRA-speak. I didn't realise you meant issue-links, so there's no child relationship. You'll need issue.getOutwardIssueLink() instead of subtasks.