Comments
-
They probably don't have "email me on my changes" set in their profile. Check that first.
-
I'm not sure you need one. If I were you, I'd read through https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs to get started, and then decide whether you need a wsdl - I've not needed one myself, but I've only done a tiny simple bit of REST coding so far.
-
I don't think it's supported at all, from what I can find. I don't think your "no option to change the .net framework" is valid - you need to upgrade to 4.0
-
Define "add a user to a project"? My best guess is that you haven't added them to a role or group that grants the right permission to do things in the project, but you need to look at their profile (roles and group membership) along with the permission scheme for the project.
-
Atlassian's release policy is "when it's ready", so you won't get a firm date, other than "very shortly after it goes to OnDemand"
-
I think you're guessing there. The property you want is documented at https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issues
-
None. Sub-task create is limited by "must have create" and "must be able to edit". There's no workflow permission that controls it. If you put the "do not edit" property on the workflow status of "closed", that will do it.
-
No, it's illegal to do that. You need to licence each server separately. If you have two servers, each with 80ish users, then you need two separate 100 user licences.
-
No, with REST, you can't do this. REST "create issue" follows the workflow, so it creates open issues. If you need them in another state, then you'll have to move them through the workflow (REST lets you do it, but I'm not going to say it's fun, as you need to map each possible route and possibly issue several "push…
-
Spot on! Answers all the questions I was going to ask.On the down side, it means I'm stumped. I've seen it before, but only when someone has created a custom field called summary. Only other time I've seen it was with a very oddly broken plugin, but that was a long long time ago, and that plugin isn't around any more. I…
-
Hmm, that's odd. Could you show us a screenshot?
-
Sounds like you've added a new custom field - rename it to identify it and think about removing it completely.
-
This is effectively a "merge" of JIRA systems. Although there's a couple of guides on how to do that for Server versions, you actually need the Cloud version at https://confluence.atlassian.com/display/JIRAKB/How+to+merge+two+JIRA+Cloud+instances - this talks about merging two Cloud instances, but one of the steps is…
-
You need to add the application in "manage applications" inside JIRA, then you'll be asked for a licence key.
-
I assume by "starter", you mean the basic 10 user licence? You don't need to do any installations, just put the new licence key in place (admin -> licences). The software you're using is the same for evaluation, 10 users or 100,000 users.
-
There is no watcher field. It's a built-in function that is not written as a field, although it does have a lot in common with a "multi-user picker" Why are you asking?
-
I assume you mean 4.4, where Atlassian first added their workflow designer? That's been changed and improved in later releases, and the diagrams you now get are suitable for the current version - the code generating the 4.4 versions of the diagrams is either gone or changed to draw what you see now.
-
Ah, those, well, they're intended to be used by the workflow viewer in the issue view, not read directly. Is "view workflow" in the issue view not working for you?
-
I'm not quite sure what you mean by "JIRA workflow diagrams"? What diagrams, and where were you storing them in 4.(not 5 because that doesn't exist). Also, have you checked the "view workflow" option in the issue view? (You may need to add "view workflow" permission to the permission scheme)
-
There's no need for that. I'd recommend warning them - if someone is in the middle of a transition (on a transition screen) and your new workflow changes or removes that transition, they could lose what they're putting in (commit will throw a nasty error), but you won't damage any data. Workflow migration can be very heavy…
-
That is not right. You don't need a backup to run the integrity checker. The checker won't have any effect on this problem even if the status is wrong because the problem is with the resolution and not the status. Sorry, but I think you've misread the question!
-
Have a look at https://www.atlassian.com/resources/experts - select hosting and your country (if it matters to you) I'm mildly curious about "cannot survive without database access" - as you certainly can't write to Jira's database, and there are plenty of reporting options to investigate.
-
Atlassian would encourage you to upgrade on every release, but that's often not practical for several reasons. You don't want to slip too far behind - the larger the upgrade jump, the more work it is, smaller increments tend to be easier. Most of the time, you see people upgrading on a 6-12 month frequency though, and…
-
The assignee field is limited by permissions. The watchers field could be anyone - that's the point of it - it could be anyone in the system. If you removed the requirement to "browse all users", then the watchers field would let you browse all the users by definition...
-
The quickfilters only really kick in when you use them. I find the main things that load a board are the baseline query and (to a lesser extent) the swimlanes, as they're all directly involved in the rendering up-front. 30 seconds a click is by FAR too slow. To investigate, could you try a quick test - create a new board…
-
"Workflow in issues section" does not mean a lot I'm afraid. The extensions plugin mostly adds some conditions, validators and post-functions which you select when editing a workflow. Have a look at the transitions in your workflows when in edit mode and try adding some - you'll see more options there.
-
I've seen systems with over 300, but this was because someone thought it was a good idea to give all the PMs admin rights so they ran off and did their own thing. Part of my housekeeping was to get it down to something around 50 (I think there were another 20ish we could have merged if the data wasn't so complex, so it…
-
It reads the history (select from changeitem and changegroup, if I understand correctly) and does the calculation in code. If you're looking at the "time in status" field, it stores the results in the index, but if you're looking at the transistions tab from the JIRA Toolkit, I think it does it on read/display. This is one…
-
No, it's not stored, it's calculated.
-
What does the log say? Not getting data on the history tab is consistent with data not going into the changeitem table, so I think that's the starting point, but your log should tell you why it's not updating - also, check all the actions that should be doing an update.