I have worked on Atlassian Jira for few years.
I have started exploring asana for tech project management; currently, I am the only user in the project.
When I create the tasks, I have to manually select the assignee to myself.
How can I set the default assignee to myself?
Thanks.
There is no way to set a default for all task assignment. Automatic task assignment depends on the context of where you create the task.
When you click the orange + button on the Asana top bar and then click to create a new task, the resulting task will automatically be assigned to you. Also, if you are in the 'My Tasks' section of Asana, hitting 'return' will create a new task automatically assigned to you.
If you are creating tasks by hitting 'return' in a project, you can use the keyboard shortcut 'Tab-M' to assign the task to you.
Related
I try to use "schedule task" on eaver. So, I make my "database task". When I right click on a task to set the schedule, there is no "scheduler" button. The options to click on are:
"Run task, Edit task, Create new task, Copy task, Delete, Create new task folder, rename folder, group task by category, group task by type, copy, configure column, auto-size column"
The version is 22.3.1.
Is there anything that I have to download or set before these steps? what is wrong?
After facing the same problem, I found the reason. The scheduler feature is only available on the enterprise and ultimate versions of DBeaver."
On the following link, scroll down and click on Administration & Security tab to check the difference between edition:
dbeaver.com/edition
I want to prevent my users from logging work once an issue gets to a particular status. How can I accomplish this?
I have a post-function in my workflow that sets the Resolution, but the "Log Work" item in the More menu still shows up.
I don't see in the Project or System administration any options about it.
You can accomplish this by setting jira.issue.editable to false in the properties of the status in the workflow.
Find the active workflow that applies to the issues you wish change. This is most easily done by either: going to the 'Workflow Schemes' admin page, then clicking on the Workflow link in the row applying to the issues' project and issue type, or clicking View Workflow in the Issue View.
To edit the workflow, you will need to either create a copy of it (if using the default jira system workflow) or edit the draft of the workflow.
In the Workflow Editor, for the 'Closed' step, click View Properties (in Text mode) or Properties (in Diagram mode) to see the step properties.
Editing issues in the selected step is enabled by default, or you will see a jira.issue.editable property with value true. Either create the value or chang the property value to false.
Publish your draft workflow, or if editing a copy, activate the workflow by creating a new workflow scheme associated with the edited workflow, and then associating it with your project.
Reference: https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html
Does TFS 2013 have the ability to automatically add Templated tasks to a work item?
So I create a work item, it automatically adds some tasks for it such as Code, Test, CodeReview, HelpGuide
Can you guide me to the right place to read about it if it has this ability.
Built-in? Then no.
There is an open source TFS Serverside plugin, called TFS Aggregator which will allow you to run a piece of code every time a workitem changes. Creating subtasks when a parent task changes state or is created is a piece of cake.
See:
https://github.com/tfsaggregator/tfsaggregator/releases
https://github.com/tfsaggregator/tfsaggregator/wiki/Auto-Create-Children
If you don't want to run a server side handler, then you may be able to use a script (powershell can do pretty powerful things when using the Client Object Model).
Or you can use the copy-paste magic of the Excel plugin for TFS. Simply put the tasks you want to create on the clipboard (without an ID) then use the "Insert Rows" paste option to paste them directly under their prospective parent (in a tree based query). Upon publishing the tasks will be associated to the parent. Play with the Title 1, Title 2, Title 3 etc fields to control the nesting.
In my implementation of JIRA, I have a custom field called Developer which gets populated automatically (username) whenever someone move the JIRA from Open to Fixed state. Now I want something similar for the Fixed to Reopen transition. That is, whenever the tester changes the status to Reopen, it should go back to the Developer or the Project Lead (in case the field isnt populated as the custom field can be overridden).
I tried to implement a post function, but there isn't a way where I can use OR criteria. Or is there a way?
You can do a Post Function on the transition using the Script Runner plugin if its a self-hosted JIRA instance which will allow you great flexibility in the logic to fill the target field in.
I finally managed to find a workaround for this.
Download the Workflow Enhancer for JIRA plugin (FREE). You would also need JIRA Suite Utilities (I had it installed already for some other customization)
In the Fixed to Reopen transition, add a Post Function and use Copy Value From Other Field to update Assignee from Developer field
Then add another Post Function underneath this where you need to use Universal Post Function. Here make the boolean condition as {Assignee}=="" and select Choose post function to execute: as Assign to Lead Developer
Publish the draft.
How to go about renaming a job in jenkins?
Is there another way than to create a new job and destroying the old one?
In Jenkins v2, in your dashboard or job overview, click right button on the job and select rename:
In the version we're running (1.480) it is simply a matter of changing the Project name in the Configure menu and hitting Save afterwards.
Cheers,
In New Jenkins, Click Rename link present in the left navigation pane, Update the job name and click save.
Simply change the name in the Pipeline/Project name and hit save.
Note that if your browser window isn't wide enough the "popup" below will be offscreen so make sure you scroll down or your jobs may mysteriously not rename.
"Are you sure about renaming old-job to new-job?"
Use the "Configure" option to the left:
Example showing Configure option
(Sorry, first few posts so I'm not able to post images in directly yet!)
If you can't see this then make sure you have access rights - in other words, you may need to be logged in, and you will need privileges that allow you to administer that job/pipeline.