Comments
-
Hi Christian, Yes i know, it can be a private filter as well, but the owner of the filter has raised this query that he can't access the filter. I have updated the question.
-
Hi Robert, My bad, the sprint wasn't deleted after it's closed, yes the documentation statiing - ""Closed sprints cannot be deleted." is correct
-
I was able to remove a completed sprint which didn't have any issues. you have mentioned your JIRA version but the bug is with the JIRA Agile (greenhopper) version whose link i shared
-
i just tested a similar scenario in my test machine, it works fine at my side. I am using JIRA Agile version - 6.3.6.1 Which version are you using? there is a known issue as well - https://jira.atlassian.com/browse/GHS-9036
-
People facing similar issue here (see comments) https://confluence.atlassian.com/display/AGILE/Deleting+a+Sprint
-
You don't need script runner for this - I have asnwered this questione before, please go through my answeres and comments - https://answers.atlassian.com/questions/157110/transition-parent-to-close-when-sub-tasks-are-closed-is-not-working-the-way-it-should
-
Not currently - https://www.atlassian.com/licensing/service-desk Note: JIRA Service Desk is a plugin for JIRA. The JIRA Service Desk license type and user count must match that of the JIRA license it is being used with. For instance, a 25 User Commercial JIRA license will require a 25 User Commercial JIRA Service Desk…
-
Are you behind a firewall? Lot of people improved their onDemand speed when they fixed their firewall settings.
-
Hi Irtiza, Can you Please share the complete code sample for making http call from a post-function. Thanks,
-
Being frustrated doesn't help, can you please elaborate your problem, to whom you want to send the notification and you mean the reporter is not getting notified, please patiently explain the whole problem.
-
Good question, it's a highly requested feature and currently not implemented, please see here - https://jira.atlassian.com/browse/JSW-4686
-
It's an open request - https://jira.atlassian.com/browse/JRA-6851
-
That's why it's better to use Story points for estimation, because even though you have same tasks but different teams are working on it (Android, iOS) as the final work is for 2 different platforms thus the efforts of both the teams should counted towards the final burndown. My suggestion is to move to story points…
-
You can add that custom field in the "create screen" of the issue and make that custom field mandatory. This is built-in functionality and doesn't need any plugins.
-
thanks, global transition was easily delted from workflow designer.
-
If you have admin rights press "g +g " and then start typing story...
-
Good to know - if you have a behaviour associated with a field, it should disable inline editing on the View Issue page
-
you have to change the underlying workflow of the project, as the board's workflow is based on the project's workflow
-
You can add a transition screen and make sure the fixVersion is mandatory in that transition screen. And this transition screen should be added when the issue goes to closed.
-
Why not use the shortcut? , just press the "." (dot) on the issue screen and start typing whatever you wish to do on the issue and all the options are visible in a drop down , create sub-task, move, workflow transitions etc, everything is available.
-
Here - https://marketplace.atlassian.com/plugins/com.intenso.jira.issue-templates/versions It only supports JIRA 5.x, we have used inhouse built plugin for jira (4.4.4).
-
A cooler way -- write a nice script in ruby/python which does REST calls to make sure both projects are in sync and issues are imported from one project to another and you can decide in the script to remove redundant fields of source project.
-
here are the docs - https://thepluginpeople.atlassian.net/wiki/pages/viewpage.action?pageId=35782663
-
here are the docs - https://thepluginpeople.atlassian.net/wiki/pages/viewpage.action?pageId=35782663
-
Yes you are right about achieving this feature using plugin. Here's the cloud version of it - https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui/cloud/overview
-
You can keep track of this here, just click on vote if you want this feature and you will be added as a watcher - https://jira.atlassian.com/browse/JSW-13497
-
Hi Deepak, Generally the resolution is being manually set by someone on the "Edit" or "create" screen of the issues, thus make sure the field "resolution" is removed from the issueType screens and also make sure that resolution is not being set by any workflow transition post-function before the issue is complete. If this…
-
Hi Deepak, The strike out mean the "resolution" field is set, generally this field is set at the end of workflow but due to some bad configuration it could be getting set at initial or middle statuses of the workflow thus you see the strike out.
-
This is the permission map of the boards, i guess you should confirm against this - https://confluence.atlassian.com/display/AGILE/What+are+the+permissions+used+in+Agile+Boards
-
The reason is this ( I also faced the same issue) https://answers.atlassian.com/questions/256719/user-permission-for-sprint-planning-in-jira-agile