Restriction with Time estimation and time spending process

Zoltan Agoston February 24, 2024

Hi there, 

 

I finding a solution for the following request:

We have outsourced Developers.

We using Softwer Project to organize the EPIC and tasks.

I would like to make som limitations like:

Only ME as Developer leader can edit the Original estimate field.

The assignee can spent time on the issue only when the card is in a specified status, like In progress 

When the Original estimated time is over , then no more time tracking able to record on that issue...

 

IS there any ide or existing solution for this kind of setup ?

THX

 

2 answers

0 votes
Yuliia Hushcha _Reliex_ February 26, 2024

Hi @Zoltan Agoston 

You can configure it via Jira permissions. Good luck! 

0 votes
Maria
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 25, 2024

Hi @Zoltan Agoston 

It's Mary from Planyway for Jira: workload, roadmapping, time tracking

 

To achieve the level of control and customization you're looking for in Jira, you'll need to leverage a combination of Jira's built-in permissions, workflows, and possibly some marketplace plugins for finer control over time tracking and field editing permissions. Here’re some ideas:

1. Restrict Editing of the Original Estimate Field

To restrict editing of the Original Estimate field to only the Developer Leader (you), you would typically use a field-level permission scheme. However, Jira does not support field-level permissions natively. You can work around this by:

  • Using Workflow Properties: You can use workflow properties to make a field read-only for certain statuses. However, this won't limit the ability to edit the field to a specific user or role directly.
  • Marketplace Plugins: Plugins like ScriptRunner can help. For example, you can create a script to check the user's role before allowing them to edit certain fields.

2. Limit Time Tracking to Specific Issue Statuses

To ensure that time can only be logged when an issue is in a specific status (e.g., "In Progress"), you can:

  • Customize Workflows: Edit the workflow associated with your project to add a condition on transitions that only allows logging time if the issue is in the correct status. 
  • Use a Plugin: Some marketplace plugins offer enhanced time tracking controls. Tempo Timesheets, for example, provides features that might meet your needs, including more granular permissions and conditions for logging time.

3. Prevent Time Tracking After Original Estimate is Exceeded

Preventing further time logging once the original estimated time is exceeded is not a standard feature in Jira. To implement this, consider:

  • Automation: Use Jira's automation rules (Project settings > Automation) to monitor time tracking fields. You can set up a rule that checks if the logged time exceeds the original estimate and then transitions the issue to a status that doesn't allow further logging.
  • ScriptRunner: With ScriptRunner, you can write a custom script that checks the logged time against the original estimate and prevents further logging if the limit is reached.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events