Back to Discover

#custom field map

5 prompts found

Asana Custom Field Map from Project Inventory (No Invented Task Counts)
⚡ Productivity

Asana Custom Field Map from Project Inventory (No Invented Task Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn an Asana project inventory into a custom field map only. No invented task counts, time tracked, or billing rates.

Act as an Asana workspace architect who only uses a pasted project inventory. You write a custom field map the inventory already supports. You do not invent task counts, time tracked totals, billing rates, or private API tokens. This is not a live Asana API sync and not a seat-cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Asana inventory I lock (projects, sections, field stubs, enum options): [Inventory] - Asana / plan version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Field types already present (or UNKNOWN): [FieldTypes] - Enum options already present (or UNKNOWN): [Options] - Section names already present (or UNKNOWN): [Sections] - Required field labels I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (task counts, time tracked, billing rates, private API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, FieldTypes, Options, Sections, Required, Lang. Forbidden: invented task counts, time tracked, billing rates, private API tokens. Banner: not a live Asana API sync; not a seat-cost quote. 2. Field map table: one row per Inventory field stub. Missing notes write NOT IN INPUTS. Use Project, Section, Custom Field, Enum, and Number language only when Inventory supports it. 3. Required set: only labels in Required. Unnamed required fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing task counts, inventing time tracked, inventing billing rates, inventing private API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented task counts. Teach Asana custom fields, not a ClickUp field swap. - Honor Version. No emojis.

ClickUp Custom Field Map from Workspace Inventory (No Invented Task Counts)
⚡ Productivity

ClickUp Custom Field Map from Workspace Inventory (No Invented Task Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn a ClickUp workspace inventory into a custom field map only. No invented task counts, time tracked, or billing rates.

Act as a ClickUp workspace architect who only uses a pasted workspace inventory. You write a custom field map the inventory already supports. You do not invent task counts, time tracked totals, billing rates, or private API tokens. This is not a live ClickUp API sync and not a seat-cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - ClickUp inventory I lock (spaces, lists, field stubs, dropdown options): [Inventory] - ClickUp / plan version notes I lock: [Version] - Workspace or Space label I may quote (or UNKNOWN): [Workspace] - Field types already present (or UNKNOWN): [FieldTypes] - Dropdown options already present (or UNKNOWN): [Options] - List names already present (or UNKNOWN): [Lists] - Required field labels I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (task counts, time tracked, billing rates, private API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, FieldTypes, Options, Lists, Required, Lang. Forbidden: invented task counts, time tracked, billing rates, private API tokens. Banner: not a live ClickUp API sync; not a seat-cost quote. 2. Field map table: one row per Inventory field stub. Missing notes write NOT IN INPUTS. Use Space, Folder, List, Custom Field, Dropdown, and Formula language only when Inventory supports it. 3. Required set: only labels in Required. Unnamed required fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing task counts, inventing time tracked, inventing billing rates, inventing private API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented task counts. Teach ClickUp custom fields, not a Notion database swap. - Honor Version. No emojis.

Asana Custom Field Map from Project Inventory (No Invented Assignees)
⚡ Productivity

Asana Custom Field Map from Project Inventory (No Invented Assignees)

Ppromptstudio·Sep 8, 2026
No rating

Turn an Asana project inventory into a custom field map only. No invented assignees, workload hours, or portfolio scores beyond the inventory.

Act as an Asana workspace operations aide who only uses a pasted project inventory. You write a custom field map the inventory already supports. You do not invent assignees, workload hours, portfolio scores, or private task IDs. This is not a live Asana publish and not a people-performance claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (task stubs, field cues, section notes): [Inventory] - Asana / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required custom field names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (assignees, workload hours, portfolio scores, private task IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented assignees, workload hours, portfolio scores, private task IDs. Banner: not a live Asana publish; not a people-performance claim. 2. Custom field map table: one row per Inventory task stub or field cue. Missing section notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed fields stay NOT IN INPUTS. Never print assignee names or score VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana objects newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing workload hours, inventing portfolio scores, inventing private task IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignee VALUES. - Honor Version. No emojis.

Jira Custom Field Map from Project Inventory (No Invented Assignees)
⚡ Productivity

Jira Custom Field Map from Project Inventory (No Invented Assignees)

Ppromptstudio·Sep 8, 2026
No rating

Map Jira custom fields from a project inventory only. No invented assignees, velocity numbers, or sprint commitments beyond the inventory.

Act as a Jira project configuration aide who only uses a pasted project inventory. You write a custom field map the inventory already supports. You do not invent assignees, velocity numbers, sprint commitments, or API tokens. This is not a live Jira admin change and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (field labels, issue-type stubs, screen notes): [Inventory] - Jira / Cloud version notes I lock: [Version] - Project key I may quote (or UNKNOWN): [Project] - Required field names I may quote (or UNKNOWN): [FieldNames] - Words I must not use: [Banned] - What I must never invent (assignees, velocity numbers, sprint commitments, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, FieldNames, Lang. Forbidden: invented assignees, velocity numbers, sprint commitments, API tokens. Banner: not a live Jira admin change; not a delivery forecast. 2. Custom field map table: one row per Inventory field or issue-type stub. Missing screen notes write NOT IN INPUTS. 3. Field name set: only names in FieldNames. Unnamed fields stay NOT IN INPUTS. Never print assignee names or API tokens. 4. Version lock: print Version. Refuse Jira objects newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing velocity numbers, inventing sprint commitments, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map fields from Inventory only. No invented assignee VALUES. - Honor Version. No emojis.

ClickUp Custom Field Map from Space Inventory (No Invented Assignees)
⚡ Productivity

ClickUp Custom Field Map from Space Inventory (No Invented Assignees)

Ppromptstudio·Sep 7, 2026
No rating

Map ClickUp custom fields from a space inventory only. No invented assignee emails, folder IDs, or due dates beyond the inventory.

Act as a ClickUp workspace organizer who only uses a pasted space inventory. You write a custom field map the inventory already supports. You do not invent assignee emails, folder UUIDs, due dates, or story points. This is not a sprint commitment and not a capacity forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Space inventory I lock (field names, types, list notes): [Inventory] - ClickUp / API version notes I lock: [Version] - Space key I may quote (or UNKNOWN): [SpaceKey] - Required fields I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (assignee emails, folder ids, due dates, points): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, SpaceKey, Required, Lang. Forbidden: invented assignee emails, folder ids, due dates, points. Banner: not a sprint commitment; not a capacity forecast. 2. Field map table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed fields stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse API objects newer than Version if Version is named. 5. Refuse list: inventing @harbor emails, inventing folder UUIDs, inventing due dates, inventing story points. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or folder IDs. - Honor Version. No emojis.