The requirement people assign me jira tasks to implement some issues or to fix bugs and when I have implemented the task, I assign the task to some tester.
Now I would like to find out, which tasks was assign to me in the current project / release to check the documentations. Any Idea how to do this? the "Assigned to Me" widget in jira shows me only the tasks, which are currently assigned to me.
Open Filter in JIRA. Create a filter with following query
assignee = currentUser() AND resolution = Unresolved order by updated DESC. It'll show you all the unresolved issues in JIRA, that's assigned to you. But make sure that you have logged into JIRA, with your credentials.
Related
I'm interested in using Graph API in order to manage tasks within MS To do. I've already found documentation for creating a new task.
However, I didn't find anything about the following during a new task creation or task update:
Is it possible to set subtasks on a task?
Is it possible to set a category on a task?
Is it possible to reassign a task?
Maybe someone has information about it.
As of now there is no way you can create sub-task with Microsoft
Graph. There is a feature request already present
here,
please upvote it so that product team may consider it for
development in future.
For category as well we cannot get or set the data as of now. For
this as well there is a feature request
here.
Please upvote it.
For the assignment as well there is a uservoice
here.
Please upvote it so that it may be implemented in future.
I'm using the JIRA Agile plugin.
I've created a task with a few subtasks inside it and I want to assign multiple users to one subtask.
Any idea how this is possible without rebuilding JIRA from source then tinkering the code?
There is an Atlassian page that covers this topic.
The options they discuss may not match your requirements though. They seem to be focused on the situation where the users you assign to an issue are consistent and part of a group.
One option is to create a custom field of type 'group picker'. Another option is to have a user defined on JIRA that actually represents a group of users and has a mailing list email.
I have a requirement on a project that a ticket which is a Blocker should be assigned to ABC user, ticket which is a Major should be assigned to DEF user, so on.
Has anyone implemented a worfklow in JIRA which does something like this? I know you can design a workflow which can assign a ticket to the user based on the type of the ticket but based on the priority can you assign a ticket to a user? Please help.
JIRA comes with components and component leads, and if you leave the assignee at Automatic then the newly created issue will be assigned to the appropriate component lead. I'm not sure what you mean when you say that JIRA can assign based on issue type.
Assigning according to Priority means that you have to trust the person setting the priority. Also, you have to be able to configure the mapping from Priority to Assignee somewhere and then be able to change that mapping later on.
To assign according to priority I would use a custom Script Runner post function on the create transition of the workflow in use.
I'm trying to use JQL to measure cycle times (the Control Chart has other issues), so I need to get the date that an issue changed status. I see that one can use the CHANGED keyword to filter issues that have changed status on certain dates, but I see no way to actually list the date of the change as a column.
Any ideas? How would you guys address this lack of visibility into cycle time data?
There is no simple solution available in JIRA at the moment. See the issue https://jira.atlassian.com/browse/JRA-12825 for the whole discussion. The argumentation of Atlassian is the following:
There exists a product Service Desk that implements the SLA feature expressed here.
There are reports and additional plugins available that give similar information to this. See the JIRA Suite Utilities which give you a UI for each issue to see the transition summary.
JQL (JIRA Query Language) was intended to select all issues that match a query, not to select special information to these issues. You have to use the configuration of the table, if it is included there as a field of the issue (which it is not).
In addition to the suggestions from mliebelt there is another at https://answers.atlassian.com/questions/128370/how-to-capture-date-of-state-change-in-jira. It requires JIRA Misc Workflow Extenstions and uses the "Copy value from field to field" function to capture the transition date in a custom field.
There is a plugin in Atlassian Marketplace called Time in Status just for that purpose. The plugin prepares a report on how much time each issue spent on each status or assignee.
Time in status is useless if need to count of Jiras that changed status on that day. Time in status widgets is useless for this
I am using Jira for organizing user stories for my project on Agile approach. When I tried to close a user story it shows the status as ' Resolved', rather than 'Closed'.
Can someone help me how to change the user story status to closed?
Please post your suggestions and help.
Its a bit hard to answer such a vague question - so if you can ellaborate a bit on the customization you have done in your JIRA instance, it can help.
Some pointers:
JIRA is using workflows to manage the flow an issue can use.
The default workflow that comes with an installation of JIRA is called "jira" and looks like this: https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
Depending on the customization of your JIRA installation, you can either change the workflow to go from Open to Closed when you use the "Resolve" operation.
If you are not the JIRA administrator, different workflow transitions can have various properties and conditions and validators set on them, for example checking for permissions. So if you are a user that does not have permissions to do a certain transition - you can see if you can change it via the permissions administation panel, or again - in the workflow validations.